| Table of Contents | ||
|---|---|---|
|
...
The Approval Workflow will be enabled only if the eSignature package is purchased. The Approval Workflow can be enabled project-wise.
Enable eSignature Feature
...
Approval Levels and Mechanism
- If you have the eSignature feature enabled even before QMetry Test Management v8.8, then your existing test case and test suite approvers will be carried forward at Level 1 in respective sections.
- Maximum 5 levels can be added for Approval Workflow, the settings are done from Customization > General Settings & Audit > General Settings.
- Customization “Modify” rights are required to be able to add/remove levels.
- In the General Settings section of the project, the admin defines the frequency to send a notification to reviewers/approvers of pending level.
- The entity will be considered as approved only on approval at all the defined Levels, else the entity will be displayed in an In-review state.
- In case the entity gets rejected later on at any of the levels, it will be moved back to the first level of approval i.e. In Review state.
- There can be multiple approvers/reviewers at each level. But to mark an entity as approved, approval from a single approver is required. The entity will then move to the next level of approval.
- During the approval process, if users make any change to the entity, the entity will be moved back to the first level of approval irrespective of its current level of approval. All the approvals of that entity will be revoked.
- You can not add the next level when the lower level does not have reviewers/approvers in it.
Whenever assets are reviewed/approved, a notification is sent to reviewers/approvers of all levels except the one who reviewed/approved the assets and to Created By, Watchers, Owners of those assets.
QMetry sends a notification to the "Created by" user when reviewers/approvers reject an entity with Request Change.
Approval Access
Refer to Approval Access to read about:
...
- Request Change: If the reviewer wants some modifications in the requirement, then they can ask for the required change by clicking on the Request Change button.
Review at Level 2/Next Level
The requirement reviewed at Level 1 is moved to the next level for further validation. For example, to check whether the associated test cases are in sync with the modified requirements. There are two options for a reviewer at this level:
...
(A) On the requirement list view, open the Cog icon for the requirement and select Request Change.
(B) Open the requirement detail page and click on the Request Change option at the top.
When the reviewer clicks on the Request Change option, the pop-up opens to enter remarks regarding it. Add remarks and click on the Request change button.
...
You can link test suites to only those test cases which are approved. Hence, you can not execute a test case until it gets "Approved" State.
The test cases are approved version-wise and not as a whole. If the Approval Workflow is enabled and the test case version is in "Approved" state, then users can not modify that particular version of the test case. In this case, a new version of a test case can be created and that new version will be in the "In Review" state.
- If the eSignature is enabled, then shareable test cases will be created with the "Approved" State by default. Once shareable test cases are created, users can not edit the steps of a shareable test case. However, user can create a new version of the shareable test case, if required.
- If a test case is approved at all the existing levels and a new level of approval is added afterward, then the test case will be shown pending approval for the latest added level. If the test case is already linked to a test suite, then its execution will not be allowed.
- If a test case is pending for approval at the last level. If this last level is deleted before the approval process complete, then the pending approvals at the level will be marked as Approved.
- If a test case is approved at all the existing levels and a new level of approval is added afterward, then the test case will be shown pending approval for the latest added level. If the test case is already linked to a test suite, then its execution will not be allowed as it is still pending for approval for the newly added level.
...
Follow either of the ways:
(A) On the test case list view, open the Cog icon for the test case and select Approve.
(B) Open the test case with the “In Review” State.
...
When the approver clicks on the Request Change option, the pop-up opens to enter remarks regarding it. Add remarks and click on the Request change button.
Approve: The test case will be marked as Approved by the approver at <Level 1>.
The following pop-up opens asking for confirmation. Click “Yes” to approve the test case.
A pop-up opens to add remarks.
On approving test cases at one level, the email notification is sent to all the approvers of the next level in accordance with the defined frequency to send a notification to approvers of the pending level.
Approval at Level 2/Next Level
The test case approved at Level 1 is moved to the next level for review. The entity state is changed from “Pending at <Level 1>” to “Pending at <Level 2>”.
There are two options for an approver at this level:
- Approve: The option behaves the same as Level 1. The test case will be marked as Approved by the approver at Level 2.
- Request Change: If the reviewer wants some modifications in the test case, then they can ask for the required change by clicking on the Request Change button.
Request Change
...
Enable the Show history option.
The email notification about the approval status and details is sent to the "Created By" users when approvers request changes.
Approval at Last Level
Once you approve the test case, it cannot be edited further. However, you can create a new version or clone this test case.
On approval at the last level, the test case will have the Approved state.
View Approval Logs
As the test case passed through subsequent levels, the corresponding entries are displayed as Logs.
(A) On the Approval Details panel on the test case details page > Details tab
(B) On hovering the icon on the Test Case list view
See that the Orange symbol is replaced with the Green symbol after approval at all the levels.
(C) On the Change Log tab on the test case details page.
Operations on "Approved" Test Cases | Impact on Test Case State |
|---|---|
Copy | Will reset the State to “In Review” |
Move in same project | Will preserve the State |
Move in other project | Will reset the State to “In Review” |
Export | Will export the State of test case |
Re-import | Will create a new version of test case and reset the State to “In Review” |
Linking Release/Cycle/Requirement/Test Execution | Will not reset the test case State |
Adding Comments | Will not reset the test case State |
...
The following pop-up opens asking for confirmation. Click “Yes” to approve the test case.
A pop-up opens to add remarks.
On approving test executions at one level, the email notification is sent to all the approvers of the next level in accordance with the defined frequency to send a notification to approvers of the pending level.
Approval at Level 2/Next Level
The test execution approved at Level 1 is moved to the next level of approval. The entity state is changed from “Pending at <Level 1>” to “Pending at <Level 2>”.
There are two options for an approver at this level:
...
The test execution is moved back to Level 1 for approval.
The email notification about the approval status and details is sent to the "Created By" users when approvers request changes.
Approval at Last Level
The test execution is moved to the last level of approval. The entity state is changed from “Pending at <previous level>” to “Pending at <Last level>”.
There are two options for an approver at this level:
...
Approving the Test Execution Run at the last level will allow the user to update Test Case results.
On approval at the last level, the test case will have the Approved state.
Once the test execution is approved for execution, an email will be sent to its Owner/Assignee informing that it is ready for execution.
Close Test Execution
Once the approved test suite is executed, proper status is assigned and bugs are logged with relevant test cases/test steps, the test execution can be marked as "Closed" by the users with test suite approval access. Once you close the test execution, test case results cannot be modified/executed further. However, you can view the bugs and download the attachments associated with the test cases and test steps.
Use Case: The QA Manager in an organization wants to freeze the execution of the test suite once it is executed to preserve the test run and prevent any modification in the test suite run.
...
The test execution is greyed out and its status is changed to "Closed". You can view the approval details by clicking on the info icon.
View Approval Logs
As the test execution passed through subsequent levels, the corresponding entries are displayed under Change Log.
Bulk Edit
For test case Bulk Edit, users can select either "In Review" and "Approved" test cases at a time.
...