|
|
| FAQs >> What if there
isn't enough time for thorough testing? |
Risk analysis techniques should be used to determine the focus of the testing process. As it is virtually impossible to test every possible dimension of software, risk analysis is the technique to be followed in almost all software development projects.
It requires decision making capabilities, common sense, and experience. Considerations can include:
• Which functionality is most critical to the project’s purpose?
• Which functionality is the most clearly visible to the user?
• Which functionality has the highest security effect?
• Which functionality has the most expensive for the customer?
• Which features of the system are most important for the customer?
• Which aspects of the application are testable earlier?
• Which parts of the code are the most complex in terms of coding, and being prone to errors?
• Which parts of the application were developed in lesser time than required?
• Which of the features in related projects caused problems?
• Which features in the related projects suffered from maintenance issues?
• Which parts of the customer requirements are unclear or ambiguous?
• What do the developers rate as the high risk factors in the application?
• What kinds of issues will defame us the most?
• What issues are going to be the most asked by the customer service?
• What kinds of tests can test more than one functionalities of the application easily?
• Which tests will provide the best high-risk-coverage - time-required ratio?
|
| Sponsored Links: |
|
|
| << back |
|
|
|