How to do a good job of testing in the company (do a good job of testing)

How to do a good job of testing , We all know that software testing focuses on the needs of customers , Focus on the business process of the subject , I'm in my last company , Because the last company developed it independently , So the business process was soon familiar to me , Plus I'm the only one to test , I do all the work by myself , Then it is more important to do a good job for a tester. First, start with the requirements , It is necessary to thoroughly understand the requirements specification , The overall purpose of our testing is to ensure that the delivered software can be satisfied by customers , Let customers feel at ease , We can rest assured , We cannot guarantee that the software will not be defective , But at least it can satisfy customers OK

1, Understand the requirements

All the work is carried out around this demand , Dismantling is very important , In the process of requirements familiarization , What I don't understand , Be sure to find products for timely communication , Determine the results . Secondly, in the process of project development , The use cases of each issue should be summarized continuously , Learn to summarize , Make sure that there are as few omissions as possible . In fact, this is closely related to test thinking , The accumulation of work experience , And the formation of test thinking , Find the requirements related to the software entry described in the documentation , Then pay attention to the twisted nodes of each module or link step by step according to the entry .

2, Design test cases

Some companies do not write test cases , Some companies write in great detail because of their business and some requirements of Party A's company , So whether to write test cases or not , The test case is to record the test content , It avoids the omission of some test points during execution , It is also convenient for use case review , Use case summary , It can improve the later test work , Now many people use agile mode for development , Then the needs of customers will change at any time , Our use cases should be constantly updated , My project is urgent , In addition, the company's testers have less time , Using tools x-mind Divide the functional test points , In fact, in the process of designing use cases, we can have a deeper understanding of requirements , Be familiar with the function points , Make sure to cover all test points as much as possible , It is also convenient for use case review .

A： What is the key to good test cases ,

1, The key is familiarity with the system , Understanding of needs , Understanding of design documents .

2, The key of white box test case design is to cover as many internal program logic results as possible with fewer use cases

3, The key of black box use case design is to cover module output and input interfaces with fewer use cases . It's impossible to do a full test , Find the most problems in a reasonable time with the least use cases

B: A principle of test cases

1, Representativeness of test cases ： Can represent and cover all kinds of reasonable and unreasonable 、 Legal and illegal 、 Anomalous 、 Border and cross border 、 And the input data of the limit 、 Operation and environment settings, etc .

2, Decidability of test results ： That is to say, the correctness of test execution results can be determined , Each test case should have the corresponding expected results .

3, Reproducibility of test results ： For the same test case , The execution results of the system should be the same .

C: What aspects to consider in designing test cases

1, Subdivide , Based on the page element control involved in each link , We are analyzing step by step , Use equivalence classes , Boundary value and other refinement methods .

2, Interface and other aspects , For example, whether the whole interface is clean and beautiful , This kind of interface inspection is often an intuitive feeling , Most of the time, we can't express it in words , At this time, we need to have a use case displayed on the front fork page , To remind the test personnel not to forget to check the display effect of the page .

3, Ease of use , It's easy to say , It is actually a long-term accumulation process , It is more reflected in the implementation process of testers , Always find and feel the ease of use of the software from the perspective of a user . There are also various aspects that we should consider , Security , Compatibility, I will not give examples one by one .

3, The test execution

The test execution , Set up the test environment , According to your own test case, repeat the steps one by one , More careful , Although not all test cases need to be reproduced , But you must be careful when you go to the function point , Related to business processes , And the requirements specification specifies the functions to be implemented , Check for defects , The defects found are presented to the developers , Reasonable communication , You can't feel like you've found BUG Just like the air , Communication is needed ,BUG Single inside replay step , The title should be able to be read at a glance BUG The phenomenon of , There are screenshots with screenshots , There are accessories with accessories , There are logs and logs , This is also more persuasive , It can also help developers better locate and repair this problem BUG, Developers don't think so BUG Well , Go to the computer to reproduce , Obtain the basis and standard of judgment , Report reasonably , To avoid conflict .

4, Test report

Writing the test report is also an important stage , You can put what you found in this test mission BUG Make an analysis and summary , Analyze why this problem occurs , The next time there is such a problem , You can directly bring it to the developer , Just let him change , You don't have to submit defects , Although our testers' code ability is not very strong , But we have to cover a wide range , If you can understand which page and which module , The error in that code , It must be trusted by developers , Back end you can understand JAVA Logical code of , and SQL Some problems with statements , And propose optimization , You must be a good tester in the company , When you take over the project, you should slowly form your own testing thinking , Test methods can be used , But testing thinking requires experience , Have a clear mind , You can also find clues in complex work , Then you must be a great Tester , Some accumulation in the test task is recorded , It can facilitate the next test , Experience accumulation is a must for testers , Why is it said that the older the tester, the more popular it is ,IT industry 30 Testers over years old are the core backbone of the whole industry , They all have rich testing experience , A long battle , Remember to summarize what you have done in the test every day , So when you raise your salary, you can have proof , Or you've been working so long , There is no record and there will be no chance of promotion and salary increase , Write a weekly newspaper every week , Leave a mark .

5, summary

In fact, part of the test is really fishing , But you can't touch it all the time , If you touch it, you should leave a trace , At least know how to keep yourself busy in front of the boss , Software testing is a process of continuous learning , Keep improving yourself , From manual to automatic, we should constantly improve , With more and more software , The system is becoming more and more complex , Software testing is becoming more and more important in China , Traditional manual testing , We are not satisfied with today's market , But manual testing will not be replaced , Learn automation slowly after work , In the industry, software testing has not been favored , As a tester , Must do a good job of post responsibilities , That's all for today's sharing .