Exercise 15 - QA/Testing

Tests for In Progress and Completed User Stories

As part of Quality Assurance during each sprint, your team must design and execute unit tests to sufficiently test all functionality created for each user story. We often refer to this as "testing" or "unit tests". Following the guidelines from the Quality Assurance/Testing reading, you and your team will need to perform testing related steps throughout each sprint before conducting UAT in the Review phase:

• Analysis: inventory all functional requirements, features, and capabilities that are part of the sprint.  Don't forget to consider requirements from Non-Functional and Org Impact analysis as well.
• Design: using the inventory from analysis, design a plan or outline of what needs to be tested so that we know what test cases to construct and outline what test data is needed.  During this time the person designing the testing should also consider negative tests (i.e. possible steps that could break the system code) and not just positive tests which check the system is behaving.
• Construct: Create test cases to validate with positive and negative tests that all critical features function as expected as well as relevant tests of non-functional requirements.  Create test data and insert test data into the system as needed. Execute test cases and update the Test Tracker on Box about whether the test passed or failed. Upload documentation of test execution to Box. Log all failed tests, including steps to take to recreate the failed test (record as a comment on the Trello card).  

Exercise requirements

Update your Test Tracker on Box (without changing the template name) and then upload your latest Test Tracker to Canvas before class.  Make sure you use the tracker template provided to you on Box and ensure the following, up-to-date information is included:

• (for all tests) Test cases and test steps required to test completed and in progress user stories from completed and in progress sprints
• (for all tests) Identify who wrote each test case
• (for all tests) List planned test date 
• (executed tests only) Identify who ran the test
• (executed tests only) Indicate Pass/Fail and list actual results notes
• (executed tests only) List actual test date

NOTES:

• Cases should be written in a detailed way so that anyone can run them (i.e. would a new hire be able to run them without having to ask questions? Could your roommate do the same?). Don't forget login links and credentials.
• Be sure cases and test data follow good standards discussed in the reading.
• After today make sure you keep your track on Box updated always as you add tests and execute them. 
• Don't forget to upload screenshots of your executed tests (passes and fails) to Box as you execute tests.