Reprinted to 51testing: http: //www.51testing.com/html/34/n-4463534.html
Function within the system and how to test
Previously mentioned, I defined within the system, from the current mainstream language is a
java
development of web projects, each system has a corresponding different business, but management background will always be common, perhaps different product manager for system design will be different, I can extract the similarities.
If you happen to test group where no so-called process specifications, if you happen to test the system I described is the same, then take a look at the test point I offer for you.
Again, if your system is facing a huge amount of users or other users of the Internet, these test points I have provided is not enough, even when you can bring a negative example.
Three elements of internal systems, forms, lists, filter box.
Form,
Description: divided into titles, form fields and buttons, form fields, form fields but there is a terrible place, the input box or drop-down box will be infinitely more.
Test Focus: smoke, required, the only constraint.
Test Description: Test form is a very troublesome thing, usually required for each input box only, all need regular testing of the content, but if the test time is limited, you can extract a high priority to arrange several tests.
List,
Description: From the
database
bunch array fetches, showing up in some sort.
Test Focus: data accuracy, user rights corresponding data display, sort rationality, paging button functions.
Filter box,
Description: usually accompanied by a list of use.
Testing focused on: the correctness of the results of the screening, the corresponding user rights after the screening, the screening list to export.
Three functions within the system, create / edit, delete / disable export.
New / Edit,
Description: usually with a functional form.
Test Focus: smoke, the data associated constraints, the revised data is correct, check the database.
Deleted / disabled,
Function Description: tombstone typically, there will be a corresponding delete or id_show field.
Test Focus: smoke, data association constraint, delete the new, modified data is correct, check the database.
Export,
In addition to screening tests focus on export, we should also consider the relationship between the corresponding data permissions.
Two expansion modules within the system, process, report
Test engineer status and role
Thanks to a few days at the beginning of the internship transparent when people have the opportunity to test professional engineer team observed the testing process is not a test.
Before the project team did not test this post, how they test? Most of the work-sharing to test the product manager and developer, the developer after the completion of a function on demand, will carry out a self-test again, no problem after that, the release code to the test environment and inform product manager. Product Manager to the test environment to see whether the function of the expected results, suggestions that the use of, after no problem can be officially released version, contact the developer if the bug occurs subsequent change it enough.
Through the above description, there did not feel anything missing link, for the uninitiated, no problem ah, function well developed, tested also had, I can not officially released yet?
Yes, if indeed the internal system, the complexity is not high and developers <= 2, so dry it would not be affected.
However, if the system has a big problem because the code will affect the
project management
staff how to do? If the system complexity and increase the number of developers, the system can properly use it?
Before these problems do not arise, few people will be taken into account.
Even one day a fatal system bug, whether it will consider whether to complete or exhaustive test after emergency repair?
How to carry out the road test
If you are an intern, there are groups within the test site testing of senior leadership, the problem can be more than just to your "master" ask, do not be lazy to learn, practice or assessment when the "master" will not save you .
If you are within the intern, the test group only one person, I would recommend that you ran, do not listen to what the words are, of course, to first find a good job. If you can not find it ...
If you are experienced engineers or high test lead to my current state of mind and vision to think I would do?
Zero experience to a test of the company, first of all talk to superiors exchange, and his words not only to understand the current testing environment, but also to catch that user tolerance.
More fortunate is a new system from scratch, you just joined, thus reducing a lot of time and effort to understand the past content.
I personally think that, go find yourself a set of direct testing process specification is meaningless, not landing too difficult to implement, it is better to start from minimized.
There are three points of the easiest to implement, raise test, hair version of the report.
Mention test,
Developed a functional test required to submit what kind of steps?
The past is a direct throw a bunch of features to you, specifically how to do, like figure,
But this may first require the development, testing needs to submit a formal e-mail, e-mail: functional, code branches, execute sql databases and other information.
According to tests provide content development, first began a smoke test, because if sql or other information is not provided, causing the test to not go, playing back test.
Fat version,
The version sent to the authority of the test system, but to do this step, you need to Git, Jenkins and linux how to use handy.
Whether a system on-line standard, the entire project team only test is the most understood.
report,
A test report is that "there is a sense of" very important work to the project team, so when updated each production environment, should make a detailed report on the content and process of this test,
As for how to write a nice test report, do not do too much elaboration.
After more than three points to do, basically we have a standardized test procedure, the test "sense of presence" has become more and more evident.
Later may be how to do?
Participation in needs assessment, perfect bug life cycle, developers respond to bug efficiency and so on.
I met those dark pit
After the screening list page;
When imported data over one thousand;
Not case-sensitive password;
Database field spaces;
Increased screening items, as well as the screening test screening + export;
My expectations & end
Having said that, be also considered Tucao lessons learned, once again grateful to have patience to see here.
In fact, many of the accidents (bug system) can be avoided, after all test work is for the user, "Ray trip"
If you have the opportunity to test these structured process, my expectations are not only standardized test processes and systems, and can even be extended to the entire project cycle.
I talk about expectations for the future system of it.
The system features new update bulletin
Internal system in time on the line, there will always be a bunch of functions and lack of impact was little bug, such as a list filter box is not functioning, users discovered the problem in time for the first time, and certainly after a long for a long time I will not use this filter again.
On the login page or the home page, plus an update announcement for each iterative development of new features and bug fixes, whether anyone will open, at least, represents a group project sincerity and in some cases also indirectly shows the work content.
Time on-line system can be integrated by the test
When the system is on the line, really should not be able to say a word or two quasi things, to evaluate the development of the development time, test time to assess the test, plus Product Manager docking combing operation of the server demand as well as some of the preparation of these things are very takes time.
For the test, the test work includes preliminary information gathering, testing, analysis,
test cases
, test purposes, bug tracking feedback and the final test report.
I hope in the future, on-line time to be tested.
Above, I am some insight about the "internal system"