What if there is not enough time for adequate testing?

Use risk analysis , Determine the focus of the test

There are few opportunities to test all possible applications ( Include all possible combinations of events 、 All the correlations 、 Or anything that could go wrong ), For most software development projects , It is appropriate to use risk analysis .

This requires judgment skills 、 common sense 、 Feeling and experience . If there is a good reason , Formal methods can also be used . The following factors need to be considered ：

1. For the purpose of the project , Which function is the most important ?
2. Which features are most obvious to users ?
3. Which function has the greatest impact on safety ?
4. Which features are most useful to users ?
5. For customers , Which part of the application is most important ?
6. In the development process , Which part of the application can be tested first ?
7. Which part of the code is the most complex , It is easy to cause errors ?
8. Which part of the application was developed in an emergency or panic situation ?
9. Which part of the program is similar to the part that caused problems in previous projects / of ?
10. Which part of the program is similar to the one that required a lot of maintenance in previous projects / of ?
11. Those parts of the requirements and design are not clear or easy to read ?
12. What parts of the application do developers think are high-risk ?
13. What problems can cause the worst distribution ?
14. What problems can cause users to complain about most ?
15. Which tests can easily cover multiple functions ?
16. Which tests take the least time to cover tests in high-risk areas ?

What if the demand keeps changing ?

This is a common headache .

1. If possible , Get in touch with the people who take the risks of the project as soon as possible , To understand how the requirements will change , Thus, the test plan and strategy can be changed as soon as possible .
2. If you consider more adaptability in the initial design of the application , In the future, when the requirements change , You don't have to do much for change .
3. Good code comments and good documentation help developers make appropriate changes .
4. Whenever possible , You should use rapid prototyping (rapid prototyping), To help users confirm their needs , Thus reducing changes .
5. Allowance should be made in the project schedule , To cope with possible changes .
6. Try to incorporate new requirements into the application software “ The next edition ”, And take the original requirements as “ The first edition ”.
7. Through negotiation , Include new changes that are easy to implement in the project , The new requirements that are difficult to realize are included in the later versions of the application software .
8. Make sure that customers and management understand the impact of changes on the schedule 、 The risks 、 And a large amount of capital consumption caused by changes .
9. When dealing with changes , There should be a balance between efforts to establish automated testing and efforts to retest .
10. When designing automated test scripts , Try to give it some flexibility .
11. When automatic testing of application software , Focus on what seems unlikely to change .
12. Conduct appropriate risk analysis for the change , To reduce the requirements of regression testing .
13. There should be some flexibility in designing test cases . It's not easy to do that , So reduce the level of detail of the test case , Or just build advanced, general-purpose test plans .
14. Pay less attention to detailed test plans and test cases , Focus on specialized tests (ad hoc testing) On .
15. How object-oriented design affects testing ?
16. Good object-oriented engineering makes it possible to trace internal design from code 、 And then to functional testing , Finally, trace back to requirements , Become an easy thing .

Because it has little effect on black box testing ( No need to know the internal design of the application software ) , The white box test only aims at the object of the application software . If the application software is well designed , Test design can be simplified .

Finally, thank everyone who reads my article carefully , The following online link is also a very comprehensive one that I spent a few days sorting out , I hope it can also help you in need ！

These materials , For those who want to change careers 【 software test 】 For our friends, it should be the most comprehensive and complete war preparation warehouse , This warehouse also accompanied me through the most difficult journey , I hope it can help you ！ Everything should be done as soon as possible , Especially in the technology industry , We must improve our technical skills . I hope that's helpful ……

If you don't want to grow up alone , Unable to find the information of the system , The problem is not helped , If you insist on giving up after a few days , You can click the small card below to join our group , We can discuss and exchange , There will be various software testing materials and technical exchanges .

Typing is not easy , If this article is helpful to you , Click a like, collect a hide and pay attention , Give the author an encouragement . It's also convenient for you to find it quickly next time .

Self study recommendation B Stop video ：

Zero basis transition software testing ： Self taught software testing , Got the byte test post offer, Is the B The best video station ！

Advanced automation testing ： Huawei has landed , Salary increase 20K,2022 Most suitable for self-study python Automated test tutorial , Spend it yourself 16800 Bought , Free sharing