The document outlines a simplified test strategy for Parttrap that involves identifying test scenarios for each user story created for each sprint and commenting on the testing status in Jira. Testing will be done on both internal and test servers with separate comments added to track the test status under each user story, and any issues will be logged separately in Jira.
The document outlines a simplified test strategy for Parttrap that involves identifying test scenarios for each user story created for each sprint and commenting on the testing status in Jira. Testing will be done on both internal and test servers with separate comments added to track the test status under each user story, and any issues will be logged separately in Jira.
The document outlines a simplified test strategy for Parttrap that involves identifying test scenarios for each user story created for each sprint and commenting on the testing status in Jira. Testing will be done on both internal and test servers with separate comments added to track the test status under each user story, and any issues will be logged separately in Jira.
things we have tested and how much coverage we will be having.
Test Scenarios will be
identified and once the testing for particular user story is completed, they will be listed out as comments in Jira against each user stories. User Stories will be created for each sprint.
Testing will be done in
both servers (Int and Test) and seperate comments will be added regarding the status of test under each user stories.