Tester workflow

Before Task

1. Pick up task in stand up which is Ready For QA.
2. Go through the card details assigned.
3. The Acceptance Criteria should be clear
4. The scope of the ticket should be clear
5. Document the test cases according to the Acceptance Criteria in the same card itself.
6. Make sure Dev-box testing is done before moving card to In QA.
7. Test cases are to be updated in the relevant card before Dev-box
8. During dev-box testing, Dev and QA should pair
9. Acceptance Criteria and test cases should be marked with Pass/Fail status before calling Dev-box done.
10. In case of any bugs, report it and after the fix - repeat Step 7.

While on Task

1. Make sure PR is reviewed and changes are done.
2. Go through the PR and files changed, to be aware of config changes.
3. Make config changes if any and install the beta version of framework (which will be released by a developer), and deploy feature branch to staging. Staging Deploy can be done from the link provided below.

• BlackKnight Staging

4. Test the feature with different scenarios.
5. Report bugs if any in git hub in same card.
6. If it is a minor bug not effecting any major functionality, then new bug card should be created with PM's approval.
7. Same feature and regression testing should be done on Beta (If we create one in future).
8. Move card from In QA to QA Complete.
9. Get in contact with the Developer to release a prod version of Framework.

After Task

1. Send release notes over mail.
2. Mail the clients to install the latest version of Framework and its related changes.
3. Regression testing should be carried on production.
4. Close the ticket card once a prod version of Framework is released.
5. Card should be moved from QA Complete to Live.