Q- I am a test engineer working on Windows applications. I do manual testing. In the agile world, when things keep on changing every now and then, it's difficult to get well-defined requirement specifications from developers, which disturb test case writing, traceability, and test execution. What would be the right strategy to make sure we are delivering quality product?
If you have dynamic requirements to test software then do follow the below steps:
- Make it your plan as per list of goals
- No need to keep actual steps in you plan
- No need to write every requirement in your planed document
- Write requirement to help keep everything straight
- Summarize a group of requirements with a simple sentence
- Plan should not be documented as huge
- If the requirement changed during executing test then change it into your document
- If original requirement changed during executing test then stop testing and make new document
- Ensure that application or module is stable then update the main document (test case & traceability) and execute updated test cases and finally the sign off the document
The impact of changing requirements is greatly reduced by using this method
Post a Comment