During testing QA and other team members can test and add issues to Jira.
- Before adding an issue, user should search to see if there's already an issue.
- If there are similar issues but slightly different, user should write up a new issue and Link it to the other issue.
- If user suspects the same root cause is causing multiple problems, user should Link issues with a note as such.
- Testers should be cautious about when to contact a developer about issues found. Contact should be made when encountering problems from a predetermined high priority area or major problems impacting testing. In general, testers should consult other testers to discuss problems before going to a developer. This is not to say developers should not be contacted, it's just to say to use caution and be wary of disrupting their work.
QA testing each release:
- Start by conducting a basic smoke test, quickly checking program functionality.
- Test issues noted in release notes, including a regression test of areas likely affected by the change.
- Then general regression or functionality testing of major areas.