There are two types of issues:
Issues related to evaluation tests – If your overall rating for a test is Fail, you are required to create at least one issue. This procedure details this creation process.
Ad Hoc Issues – This issue can be a question, problem, action item, or planned task. Navigate to Identifying, Creating, and Assigning Ad Hoc Issues.
. SeeEnter the following details:
Issue Name (required)
Priority (required) – High, medium, low
Owner (required) – Enter the owner name, or use search functionality to select the owner
Description – Provide any details about the issue
Compensating Controls
Potential Impact
Insert files or links on the Attachment and Links tab.
Choose Save Draft to save changes or Cancel to abort the session.
Note
If the issue was raised in error, you can void the issue before submitting your test.
Choose Submit. To understand the interaction of the test result, the individual test and step activities, and test plan attributes, see the table below.
Options |
Individual Test Activities / Steps |
Overall Test Result |
||
---|---|---|---|---|
Required |
Fail Ends Test |
Pass |
Fail |
|
Yes |
Yes |
Pass or Done (all or most activities) |
All activities pass – Test is submitted successfully. No open issues exist. If one or more activity fails, the system displays a warning that you have set the overall test result to Pass but one or more tests to Fail. You are asked if you want to submit the test as is. No – returns you to the test. Yes – allows the test to be submitted provided that no open issues exist. |
At least one activity fails – Test can be submitted after creating at least one issue. If all activities pass, the overall test result is set to Pass. |
Yes |
No |
|||
No |
No |
|||
Yes |
Yes |
Fail or Not Done (at least one activity) |
If any required test steps fail, then the overall test result must be set as Fail. Remaining steps do not need to be completed, even if otherwise required. |
Test can be submitted after creating at least one issue. |
Yes |
No |
A warning appears that you have set the overall test result to Pass but one or more tests to Fail. You are asked if you want to submit the test as is. No – returns you to the test. Yes – allows the test to be submitted provided that no open issues exist. |
||
No |
No |
|||
No |
Yes |
This combination (Required - No and Fail Ends Test – Yes) is not allowed during the creation of a test plan. |
Note
If the result for any required step or test activity is blank, you cannot submit the test. However, if at least one test activity with Fail Ends Test = Yes has already been set to Fail, all required steps and tests are no longer needed to submit your test.
After you have submitted your test, the actions depend on the Review Required setting established in the Customizing activity located at
Specify Whether Review is Necessary.Issues |
Review Not Required |
Review Required Workflow Sent to Subprocess Owner* |
|
---|---|---|---|
Approve |
Reject |
||
Enter Review Comments |
|||
Submitted without issues |
Done |
Done |
Test is returned to tester for rework |
Submitted with issues |
Workflow is sent to assigned issue owner |
Workflow is sent to assigned issue owner |
*Based upon delivered business content for roles.
If a review is required, the reviewer has visibility to the test including related issues, contextual information, and attachments or links.
If the reviewer chooses Reject, comments are required.
If approved, comments are optional.
The workflow between the reviewer and tester continues until agreement is reached and the reviewer approves the test. Each role can change only his or her own comments.