On t'internet!
An example test plan
| Test Case ID | Test Case | Expected Result | Actual Result | Test Status | Severity | Comments | JIRA Ref | Test Date | Tester | View Steps |
|---|---|---|---|---|---|---|---|---|---|---|
| ID0001 | Login as Learner | User should see profile page | User sees profile page | P | 24/05/2018 | S.C. | ||||
| ID0002 | Login as Manager | User should see the manager dashboard | User sees dashboard | P | 24/05/2018 | S.C. | ||||
| ID0003 | Reset password using 'Forgot Password' link in login page | User should see the forgot password page and on entering their email address and clicking the forgot password button should receive an email with the link to reset their password | Email not sent, no error message shown | F | Highest | IN-1011 | 24/05/2018 | S.C. |
Descriptive Title - If possible should be clear to developer what the issue is.
Test Environment - Can be test, develop or production environment. Should include OS and browser if relevant. Product version if relevant.
Bug Type
Steps to Reproduce - A set of numbered steps to accurately reproduce the bug.
Expected Results - What should have happened following the steps above.
Actual Results - What actually occured, including any error message shown or relevant code.
Severity - Highest, High, Medium, Low.
Frequency - Whether it happens everytime or intermittently.
Evidence - include screenshots of the issue, including any errors seen in the developer tools of the browser.
Shane Cleary