An example of a less rigorous test plan.
SCOPE
- The Scope of the Test Plan is to test the User Stories associated with each sprint
- The QAs will testing the user stories of one sprint behind
- The User Stories with complete Acceptance Criteria will be tested
- Developers should provide a complete walk-through of the User Stories
- The system will be treated as the Black Box
- System Test environment with application installed, configured and ready to use state
IN SCOPE
- All the user stories which have complete acceptance criteria
- User stories of one sprint behind
OUT OF SCOPE
- User Stories without complete Acceptance Criteria
- User Stories without test steps
- Acceptance Criteria not signed off by the Product Owner
- Code not deployed ins System Environment
ASSUMPTIONS
- All the conditions written in the Acceptance Criteria need to be true for the QA team to be able to proceed successfully
- Unit test should pass all the conditions holding in the Acceptance Criteria
SCHEDULES
- Test Scenario preparation time
- Test documentation – test cases/test data
- Test Execution
- Test Cycle
TOOLS
- Jira for User Stories and Acceptance Criteria
- Xray to write test cases and test execution
- Xray to create Test Plan for each Sprint
- Jira for bug tracking
DEFECT MANAGEMENT
- Defects to be raised in Jira with a status of OPEN
- Defects to be assigned to the Developer who has developed the code
- Complete defect management life cycle to be followed
- All the relevant information to be provided to the developers
- Screenshots to be provided as a proof
RISK MANAGEMENT
TEST ACCEPTANCE CRITERIA
- Development completed
- Unit Tested with pass results and results shared with the Testing Team
- Test Cases approved and signed off prior to the test execution by the Product Owner
- Test Data closer to the Production should be available prior to the test execution
- Defect triage based on the severity of the defect and approved by the Product Owner