Computer Tutorials
Earn Money From Internet
Cheap Freelancers
Ask An Expert
Register Cheap Domain
Data Recovery
Best Mutual Funds
Trading Forex Online
Cheap Web Hosting
Ajax Tutorials
Cheap Cell Phone Plans
Free Mobile Learning
Job Portal
Photoshop Tutorials
Cheap Jewelry
Cheapest Air Travel
Testing Interview Questions And Answers
|
Q: What if there isn't enough time for thorough testing?
A: Since it's rarely possible to test every possible aspect of an application, every possible combination of events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. Use risk analysis to determine where testing should be focused. This requires judgment skills, common sense and experience. The checklist should include answers to the following questions: · Which functionality is most important to the project's intended purpose? · Which functionality is most visible to the user? · Which functionality has the largest safety impact? · Which functionality has the largest financial impact on users? · Which aspects of the application are most important to the customer? · Which aspects of the application can be tested early in the development cycle? · Which parts of the code are most complex and thus most subject to errors? · Which parts of the application were developed in rush or panic mode? · Which aspects of similar/related previous projects caused problems? · Which aspects of similar/related previous projects had large maintenance expenses? · Which parts of the requirements and design are unclear or poorly thought out? · What do the developers think are the highest-risk aspects of the application? · What kinds of problems would cause the worst publicity? · What kinds of problems would cause the most customer service complaints? · What kinds of tests could easily cover multiple functionalities? · Which tests will have the best high-risk-coverage to time-required ratio? Q: What if the project isn't big enough to justify extensive testing? A: Consider the impact of project errors, not the size of the project. However, if extensive testing is still not justified, risk analysis is again needed and the considerations listed under "What if there isn't enough time for thorough testing?" do apply. The test engineer then should do "ad hoc" testing, or write up a limited test plan based on the risk analysis. |