An important technique prior to Test planning is SRS review and walk through to identify testable and any missing requirements.
I have always reviewed requirement documents and participated in walk through meetings with sprint stakeholders. What I would generally do is make note of missing/unclear requirements before Sprint planning meeting on Google docs or against the SRS hard copy.
Recently on softwaretestinghelp.com there was an article suggesting that it's always better to maintain a SRS analysis template.This document doesn't need to be very complicated and it's always best if done manually.
Pros of maintaining such a template:
- Helps identify testable requirements
- Uncovers missing requirement and is cost effective
- Ensures no requirement is missed during testing in other words ensuring maximum test coverage.
- This could be used to create Requirement Traceability Matrix later on.
- Makes one think on the number of test cases this module would involve in all and thus helps to calculate estimation basis the complexity of project.
Below is the template created after analysis of OrangeHRM 'Personal details' SRS.
https://docs.google.com/spreadsheets/d/1HBOjtSSwQWulk65dU3QVvUL-aJk3SKXX6mMc1LosUNE/edit?usp=sharing
No comments:
Post a Comment