eSignature and Approval Workflow
Security and audit compliance are critical for regulated enterprises. QMetry supports these needs with an Approval Workflow, auditing reports, and eSignatures. These features help organizations generate evidence for SOW and other audit compliance requirements.
You can approve test case executions with an eSignature. eSignature confirms that the test run was documented correctly and validates the status assigned to the test case. When users export test cases, the system also exports the Approval Status along with other test case details.
Requirement Review helps users validate requirement documents and verify associated test cases. If users import requirements from an external tracker, reviewers can validate the imported data in QMetry.
QMetry supports a multi-level approval workflow. This allows organizations to follow their internal approval policies. For example, a test case may first require approval from a QA Lead, then a QA Manager, and finally a Project Manager.
Pre-requisite
Get the eSignature package to enable the Approval Workflow. You can enable the Approval Workflow at the project level.
Approval Levels and Mechanism
If you enabled the eSignature feature before QMetry Test Management v8.8, QMetry carries forward your existing test case and test suite approvers as Level 1 approvers in their respective sections.
You can add up to 5 approval levels for the Approval Workflow. Configure these settings under Customizations. Go to General Settings and click Audit.
To add or remove approval levels, users must have Customization Modify permission.
In the project’s General Settings, the admin can define how often QMetry sends notifications to pending reviewers, approvers, and closers.
QMetry marks an entity as Approved only after all defined approval levels approve it. Until then, QMetry shows the entity as In Review.
If any reviewer or approver rejects the entity at any level, QMetry moves it back to Level 1 and changes its status to In Review.
Each level can have multiple reviewers or approvers. However, QMetry requires approval from only one approver at that level to move the entity to the next level.
If a user updates the entity during the approval process, QMetry moves it back to Level 1, regardless of its current approval level. QMetry also revokes all previous approvals for that entity.
You cannot add a higher approval level unless the lower level already has assigned reviewers or approvers.
When users review or approve assets, QMetry sends notifications to:
reviewers and approvers at all other levels,
the Created By user,
Watchers, and
Owners of those assets.
QMetry does not send the notification to the user who reviewed or approved the asset.
If a reviewer, approver, or closer rejects an entity using Request Change, QMetry sends a notification to the Created By user.
The admin can configure eSignature notifications and enable or disable event notifications from Notifications under Customizations.
Approval Access
Refer to Approval Access to read about:
Adding a New Level
Edit Level Name
Change sequence of Levels
Delete Approval Levels
Add Requirement Reviewers to Levels
Add Test Case Approvers to Levels
Add Test Run Approvers to Levels
Add Test Run Closers to Levels
Approval Workflow for Cross Projects
Approval Workflow in Project A (current project) | Approval Workflow in Project B | Linking assets of Project B to Project A |
|---|---|---|
enabled | disabled | NA (For Approval Workflow enabled projects, the Link Test Cases screen shows only those projects which has Approval Workflow enabled) |
disabled | enabled | NA (For Approval Workflow disabled projects, the Link Test Cases screen shows projects without Approval Workflow) |
enabled | enabled | Only Approved test cases from Project B |
disabled | disabled | All test cases from Project B |