Who: Full HD/QA Team
What: Final Testing of merged features/fixes before deploying
When: 3-5 days prior to every release
Why: Standard procedure in an Agile Sprint Cycle
Where: Test Environment: Regression server login
Test cards found in: vPro Regression Tests" Jira board & #smoke_test in Slack
How:
Approximately every 2 weeks (2 week sprint cycles), the Dev Team will publish all approved code from two-test.vcreative.net to the vPro Smoke Test Server.
On the vPro Smoke Test Server, the QA team will be responsible for giving the system a pre-release rundown of all the most common and day-to-day actions our users will take. This will be done over the course of 3-5 full days during "Regression Week". A notification will be posted in the #smoke_test Slack channel once deployment to smoketest.vcreative.net is complete.
The specific scenarios for the Regression Test will be detailed on the QA specific "vPro Regression Tests" Jira board.
These tests will follow the familiar workflow with one tweak. These tests are based on ROLE so that multiple QA team member can jump in at once, each in a unique User Account. Each "Demo" testing account now has a specific smoke test card, the username being the card's title. You move the card to "Currently Testing" to make sure no one else is using that same account at the same exact time.
If you find no issues stopping you from completing the steps detailed on the card, move it back to the "READY FOR TESTING" column and comment "Passed" on the card. If you are the second person to comment "Passed" in the same regression week, then move the card to the "Approved" column. If there is an issue found, move the card to "ISSUE FOUND" and report it in the #smoke_test Slack channel.
When issues are found on the Smoke Test server, you WILL be asked to see if the same issue exists on the Live server or "Prod". A Jira card will most likely be needed whether the issue found exists only on Smoke Test (will be fixed immediately for a retest and deploy in the release being tested) or if it is also found on Prod (will need to be fixed but will be scheduled in a future sprint).
- If regression issue found relating to a Regression test label card, send the test label card to “ISSUE FOUND” lane and create a separate bug card for that specific issue and post the created card in smoke_test slack channel (Contact Cyndi, Aaron or Jun for creation of a Jira Bug Card)
- Follow the Bug Card Template format when creating a new card. An example can be found here: https://docs.google.com/document/d/1UtRLrmiovecp9tAYybdaHmu6mSb0GyXQaHp3rFnbDLA/edit?usp=sharing
- The regression bug card will appear on the main board https://vcreative.atlassian.net/jira/software/c/projects/QA/boards/36
- (For Cyndi, Denis, Jun) Once the developers have fixed the regression bug card and is IN TESTING lane, test the bug card in smoke-test environment and verify if passed or failed
- Two tester required to pass the card
- If two tester voted and the card have total of two thumbs up, send the card to “READY TO DEPLOY” lane
- If failed, send the card back to SENDBACKS lane and repeat the process
- If regression issue is fixed, send the related SMOKE TEST label card that is in “ISSUE FOUND” lane to “APPROVED” lane