Introduction

Part 11 Compliance is provided to authenticate operations such as approval of test cases, approval of test executions and execute test cases when the eSignature feature is enabled for the QMetry project.

How to Enable Part 11 Compliance in QMetry?

Pre-requisite: The eSignature feature should be enabled for the project for which you want to apply the Part 11 Compliance.

Steps

Go to eSignature > Approval Access.
Turn the flag on for Part 11 Compliance on the screen.

The message pops up asking your confirmation -

"Once Part 11 Compliance is enabled, it will discontinue execution through Automation. Are you sure?"

3. Click "Yes" to proceed.

4. The Part 11 Compliance is enabled for the project.

Business Rules

When the Part 11 Compliance feature is enabled, users are asked for QMetry credentials to authenticate themselves before performing certain operations.

Test Case Operations

Testers can perform the following test case operations depending on the status of the eSignature feature, Part 11 Compliance feature, or their Approver permissions for test cases.

Operation	eSignature Disabled	eSignature Enabled but Not Authorized to Approve Test Case	eSignature Enabled and Authorized to Approve Test Case	eSignature and Part Compliance Enabled and Authorized to Approve Test Case
Create new test cases	Y	Y	Y	Y
Edit unapproved test case/test case version	Y	Y	Y	Y
Approve test cases	NA	N	Y (does not require QMetry credentials)	Y (requires QMetry credentials)
Edit approved test cases/test case versions	NA	N	N	N
Create a new version of approved test cases	NA	Y	Y	Y
Bulk Approve test cases	NA	N	Y (does not require QMetry credentials)	Y (requires QMetry credentials)

Test Execution Operations

Testers can perform the following test execution operations depending on the status of the eSignature feature, Part 11 Compliance feature, or their Approver permissions for test execution.

Operation	eSignature Disabled	eSignature Enabled but Not Authorized to Approve Test Suite	eSignature Enabled and Authorized to Approve/Close Test Suite	eSignature and Part Compliance Enabled and Authorized to Approve/Close Test Suite
Create test suite and link platform, release and cycle to it	Y	Y	Y	Y
Approve a test execution	NA	N	Y (does not require QMetry credential)	Y (requires QMetry credentials)
Close a test execution	NA	N	Y (does not require QMetry credential)	Y (requires QMetry credentials)
Execute a test case	Y	Y (can execute only Approved executions)	Y (can execute only Approved executions)	Y (requires QMetry credentials and can execute only Approved executions)
Import Test Executions	Y	Y (can execute only Approved executions)	Y (can execute only Approved executions)	Y (requires QMetry credentials and can execute only Approved executions) pop-up appears only when the status in file differs from QMetry
Bulk Execute test cases against multiple releases, cycles and platforms	Y	Y (can execute only Approved executions)	Y (can execute only Approved executions)	Y (requires QMetry credentials and can execute only Approved executions)
Bulk Execute test cases for a single platform, release and cycle	Y	Y (can execute only Approved executions)	Y (can execute only Approved executions)	Y (requires QMetry credentials and can execute only Approved executions)
Sync latest version of test case on Execution Screen	Y	Y (can sync only Approved executions)	Y (can sync only Approved executions)	Y (requires QMetry credentials and can sync only Approved executions)
Assigning/resetting a Build	Y	Y (can assign Build to only Approved executions)	Y (can assign Build to only Approved executions)	Y (requires QMetry credentials and can assign Build to only Approved executions)

Notes:

If the Part 11 Compliance option is enabled in QMetry project, then uploading automation result file through Automation API will not be allowed in the respective project.
If the Part 11 Compliance feature is enabled, then QMetry/LDAP users can do authentication. SAML users can not do authentication.
Users can not authenticate with an inactive/deleted user.
Time would be recorded as per the user profile.