Now the main question is ‘What is Software Testing Methodology?’
There is this fact that Software Testing methodology includes planning and strategy. But that does not tell how to start testing.
Which method I must use for testing? And why should I use it? Is there any universal method which I can apply to every software to test? Is it going to be obsolete as time passes? Is it applicable to complex software as well?
To answer all these questions you need to develop testing skills which would help you to come up with your own testing methods.
I being responsible tester irrespective of what software development model has been followed, I am ready to test the product once I receive the build. When I say Software Testing means I am strictly talking about Black box software testing.
Below is my testing methodology heuristic model:
1. Understand the Test Mission
2. Learn the software : Touring the features, menus, functionalities, using help file or available documents
3. Brainstorm the Ideas: make some notes
4. Look for Testability: if it is not testable then ask for testability (specially ask for Log file)
5. Learn the Quality Criteria of the product
6. Learn the available Oracles and trust your emotional oracle to find problems in the product
This is how I would do initial preparation for tests.
7. Look for Data: Understand the boundaries
8. Look for End Users : Their expectations
9. Make a list of Major Functions: Test their capabilities
10. Make a list of Error Recovery scenarios and test them one by one
11. Look for Patterns in reported bugs and collected information
12. Change Strategy based on gathered information
13. Look for New Features and New Bug Fixes
14. Consider Environment Parameters and their Configurations
15. As you progress in testing: review your test mission and strategy for better Coverage
There is this fact that Software Testing methodology includes planning and strategy. But that does not tell how to start testing.
Which method I must use for testing? And why should I use it? Is there any universal method which I can apply to every software to test? Is it going to be obsolete as time passes? Is it applicable to complex software as well?
To answer all these questions you need to develop testing skills which would help you to come up with your own testing methods.
I being responsible tester irrespective of what software development model has been followed, I am ready to test the product once I receive the build. When I say Software Testing means I am strictly talking about Black box software testing.
Below is my testing methodology heuristic model:
1. Understand the Test Mission
2. Learn the software : Touring the features, menus, functionalities, using help file or available documents
3. Brainstorm the Ideas: make some notes
4. Look for Testability: if it is not testable then ask for testability (specially ask for Log file)
5. Learn the Quality Criteria of the product
6. Learn the available Oracles and trust your emotional oracle to find problems in the product
This is how I would do initial preparation for tests.
7. Look for Data: Understand the boundaries
8. Look for End Users : Their expectations
9. Make a list of Major Functions: Test their capabilities
10. Make a list of Error Recovery scenarios and test them one by one
11. Look for Patterns in reported bugs and collected information
12. Change Strategy based on gathered information
13. Look for New Features and New Bug Fixes
14. Consider Environment Parameters and their Configurations
15. As you progress in testing: review your test mission and strategy for better Coverage
No comments:
Post a Comment