THE RAPID TESTING PRACTICE
It would help us if we scrutinize each phase of a development process to see how the efficiency, speed and quality of testing can be improved, bearing in mind the following factors:
• Actions that the test team can take to prevent defects from escaping. For example, practices like extreme programming and exploratory testing.
• Actions that the test team can take to manage risk to the development schedule.
• The information that can be obtained from each phase so that the test team can speed up the activities.
If a test process is designed around the answers to these questions, both the speed of testing and the quality of the final product should be enhanced.
Some of the aspects that can be used while rapid testing are given below:
1. Test for link integrity
2. Test for disabled accessibility
3. Test the default settings
4. Check the navigation’s
5. Check for input constraints by injecting special characters at the sources of data
6. Run Multiple instances
7. Check for interdependencies and stress them
8. Test for consistency of design
9. Test for compatibility
10. Test for usability
11. Check for the possible variability’s and attack them
12. Go for possible stress and load tests
13. And our favorite – banging the keyboard
It would help us if we scrutinize each phase of a development process to see how the efficiency, speed and quality of testing can be improved, bearing in mind the following factors:
• Actions that the test team can take to prevent defects from escaping. For example, practices like extreme programming and exploratory testing.
• Actions that the test team can take to manage risk to the development schedule.
• The information that can be obtained from each phase so that the test team can speed up the activities.
If a test process is designed around the answers to these questions, both the speed of testing and the quality of the final product should be enhanced.
Some of the aspects that can be used while rapid testing are given below:
1. Test for link integrity
2. Test for disabled accessibility
3. Test the default settings
4. Check the navigation’s
5. Check for input constraints by injecting special characters at the sources of data
6. Run Multiple instances
7. Check for interdependencies and stress them
8. Test for consistency of design
9. Test for compatibility
10. Test for usability
11. Check for the possible variability’s and attack them
12. Go for possible stress and load tests
13. And our favorite – banging the keyboard
Post a Comment