Versions Compared

Old Version 3

changes.mady.by.user Afjal Ansari

Saved on

compared with

New Version Current

changes.mady.by.user Harsh Gupta

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

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

  1. Go to eSignature > Approval Access.

  2. Turn the flag on for Part 11 Compliance on the screen.

    Image Modified

  3. 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.

    Image Modified

  4. 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.

...

    • Image Added


      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.