...
Enter Defects
Enter Defects
If you are testing a ticket during the regular sprint cycle and a test step fails or there is a different result than the expected result, then you must do the following:
1) Change the test step status to FAIL.
2) Explain the the comment what happened to explain the failure. Any details are helpful such as the environment, the username, whether you clicked and received an unexpected error message, or if the system failed to do anything.
3) Determine the status of the test case based on the failures. If the test steps that cannot be executed are part of the acceptance criteria for the Jira ticket, then the test case should have a status of FAIL. The steps that have failed should be included in a comment on the original Jira ticket for the developer to review (and also saved in the comments of the test case execution for follow-up later).
4) When a test case is marked as failed, the developer must be notified (via mention) in the Jira ticket, as well as notified in the QA Slack channel. This is the only way to ensure follow up and fixing of the issues that caused the step to fail.
5) Once the issue has been resolved by the developer, they must reassign the Jira ticket to the QA person and then the QA person must execute the test case again.
During regression testing, if a test step fails and there is a different result, or an error appears that is not expected, then a defect must be entered. The steps to create a defect are detailed below.
1) Within the test case execution, click on the Defects Column and Create New Issue.
...