When Test team send Test cases to stakeholders for review purpose, usually there is very slow response.
Many stakeholders like Dev, Architect etc. dont even bother to go through test cases to provide review comments. So, what is missing here ? while a tester(s) puts lots of effort in writing test cases, why they were not given good eye during review. Reasons can be of diffrent types
1. Stakeholders feels its not that important.
2. They think its testers responsibility to test anyway.
3. They dont want to take the pain to do the review.
4. They think tester might have covered all steps.
So how to mitigate these risks.
Prepare test cases or test scenario in form of a story and represent them in a diagram (Visio or MSPaint or MS Sketchflow). Test design flow diagram will save lots of time for Testers and stakeholder's.
Represent your test cases in form of picture and send for review. You will see the diffrence :)
Many stakeholders like Dev, Architect etc. dont even bother to go through test cases to provide review comments. So, what is missing here ? while a tester(s) puts lots of effort in writing test cases, why they were not given good eye during review. Reasons can be of diffrent types
1. Stakeholders feels its not that important.
2. They think its testers responsibility to test anyway.
3. They dont want to take the pain to do the review.
4. They think tester might have covered all steps.
So how to mitigate these risks.
Prepare test cases or test scenario in form of a story and represent them in a diagram (Visio or MSPaint or MS Sketchflow). Test design flow diagram will save lots of time for Testers and stakeholder's.
Represent your test cases in form of picture and send for review. You will see the diffrence :)
No comments:
Post a Comment