What is Part 11 Compliance? How to Enable Part 11 Compliance?

1 Introduction
- 1.1 Impact in Application
2 Steps to Enable Part 11 Compliance

Introduction

The configuration option Part 11 Compliance is provided at the project level to enable the Part 11 Compliance feature in a specific QMetry project. Users can disable the feature afterward. Enabling Part 11 Compliance will ask users to authenticate before changing the execution status.

Note: The Part 11 Compliance option will only be available if the eSignature feature is enabled in the project.

Whenever users change the execution status of a test case while test execution, an authentication pop-up appears to the user asking to provide a username and password. The operation is carried out only after the successful authentication of the user. The user authentication is asked across QMetry wherever users try to change the execution status. The purpose is to have only authenticated users in the organization change the execution status of test cases.

The Part 11 Compliance is only applicable to Test Case Approval and Test Suite Approval. The Part 11 Compliance is not applicable to Requirement Review.

Impact in Application

When the Part 11 Compliance feature is enabled, users get an authentication pop-up. They can carry out respective operations only after entering the correct username and password.

Affected Areas in QMetry	Description

Affected Areas in QMetry	Description
Test Suite module	Test Suite (with test case, platform, release and cycle associated with it) > Test Execution Tab. Select test suites to be executed and click on Bulk Execute. Update Status for a test case(s). The authentication window pops up. While importing test suite run XLS/CSV file: If the Execution Status in the file differs, then the authentication window pops up. The execution status can be changed only after entering correct username and password. In case of eSignature feature is enable: If users try to change the approval status of test execution from test suite detail page > Test Execution tab, the authentication window pops up.
Test Execution Screen	Test Suite (with test case, platform, release and cycle associated with it) > Test Execution Tab. Execute individual test suite. Update status for test cases individually or in bulk. If user sets build/change build using "Set Your Build" button, at that time there is pop-up coming and asking for confirmation on whether to change Execution status to 'Not Run' or not. If you opt to Reset the execution status, then the authentication window pops up. When syncing test cases with their latest version. Users can sync the test case with their latest version only on successful authentication. In case of eSignature feature is enable: If users try to change the approval status of the test suite to "Close" on the execution screen, the authentication window pops up.
Test Case list view	In case of eSignature feature is enable: If users try to change the approval status of test cases individually or in bulk, the authentication window pops up. The test case is approved after successful user authentication subject to the user is added as a Test Case Approver.

Steps to Enable Part 11 Compliance

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 for your confirmation - "Once Part 11 Compliance is enabled, it will discontinue execution through Automation. Are you sure?" > Click "Yes" to proceed.
The Part 11 Compliance is enabled for the project. User authentication will be asked before changing the status of test cases as well as test steps. Users can opt to disable the compliance for the test step level.
- Disable Part 11 for Test Step Level: By default, the option remains unchecked. Hence, the authentication screen pops up on the execution screen for every step for which you try to change its status. To stop asking for user credentials at the step-level execution, check the check box and enable the option. The user credentials will then be required only at the test case level execution.
  
  Notes:
- If the Part 11 Compliance option is enabled in the QMetry project, then uploading the 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.