Table of Contents |
---|
...
If users change the execution status of multiple test cases through Bulk Operation, then the authentication pop-up appears only once. Users have to enter Username and Password to authenticate themselves. On successful authentication of the user, the execution status of test case gets changed. If the user is failed in authentication, the execution status of test case will not get changed.
Timezone for Execution Status Changed By values is managed as per the location of the user.
If the Part 11 Compliance option is enabled in QMetry project, then uploading automation result file through Automation API will not be allowed in respective project.
For existing users, the Part 11 Compliance feature will be disabled. For newly created project and eSignature enabled project, this option will remain disable by default.
- If the Part 11 Compliance feature is enabled, then QMetry and LDAP users can do authentication with Username and Password/Part 11 Authentication Token. SAML users can do authentication with Username and Part 11 Authentication Token. Refer to know how to generate the Part 11 Authentication Token.
- Users can not authenticate with inactive/deleted user.
Impact in Application
When the Part 11 Compliance feature is enabled, users get authentication pop-up. The can carry respective operations only after entering correct username and password.
Affected Areas in QMetry | Description |
---|---|
Test Suite module |
|
Test Execution Screen |
|
Test Case list view |
|
How to Enable Part 11 Compliance?
...
- 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.
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.
...
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. and SAML users can not do authentication.
- Users can not authenticate with an inactive/deleted user.
- Time would be recorded as per the user profile.
API | Method Type | Request | Response |
---|---|---|---|
/rest/admin/compliance/authenticate | POST | {"username":"admin","password":"Ispl123#"} | {"success":true,"userId":1} |
/rest/admin/project/getinfo | GET | NO | Added “isPartLevelComplianceEnabled“ flag |
/rest/admin/project | PUT | Added “isPartLevelComplianceEnabled“ flag | Added “isPartLevelComplianceEnabled“ flag |
/rest/execution/matrix/updatestatus | POST | Added “changedBy“ parameter | NO |
/rest/execution/runstatus/bulkupdate | PUT | Added “changedBy“ parameter | NO |
...