Administration Guide
This guide will empower administrators to maintain their tenants, projects and users.
Q12-TMT has three different admin roles, which the user can be assigned to.
- Project admin: Manages the Project and different table views inside the Project.
- User admin: Manages the user accounts, roles and access rights.
- Tenant admin: Manages and configures the company's tenant settings.
Project admin
Unless the default settings have been changed, a project administrator has the following additional rights compared to, for example, a test manager:
- Edit project settings
- Create and edit Subprojects
User admin
The user admin can create, edit, delete, and activate/deactivate users, as well as define their respective roles and corresponding access rights. If Q12-TMT user management is used, the user's password can also be changed. The user administrator has no project-specific permissions and is not assigned to any Project.
Hint: If the Q12-TMT user management is used, the function “create” and “delete” are available. If the login is done via a user directory (e.g., AD, LDAP) or via single sign-on (SSO), these two functions are not available.
Tenant admin
The tenant admin can change the general configuration in the “tenant setting” menu. The language of created PDF files can also be specified here. They are not a direct member of a Project, but has the same permissions as a project administrator for all (Sub)Projects.
Project settings
This feature is not available for all license options.
The “My Projects” button opens the project structure, a list of all Projects and Subprojects assigned to the user. In this overview, the project settings can be opened via the context menu.
The project setting is separated into three sections:
- Test Suite
- Test Run
- Risk-based testing
For Subprojects, only the “Risk-based testing” section is displayed.
In the “Test Suite” and “Test Run” sections, the displayed columns of the respective tables can be configured.
The “Risk-based testing” section contains the keywords that are used to determine the impact value. The keywords can either be maintained manually or derived automatically from specification documents using the AI function.
The following rules apply to the keywords:
- Minimum number of characters: 1
- Maximum number of characters: 30
- Maximum number of keywords: 50
- No duplicates
Calculation of the impact
The calculation and analysis are only conducted for Test Cases where the impact slider is set to “Auto”.
The analysis begins by searching for the stored keywords (starting with the most severe) in the title of the Test Case, followed by the folders and subfolders of the Test Case. When a keyword is found, the search for the affected Test Case can be stopped and map the keyword corresponding impact score to the Test Case. If none of the keywords can be found in the fields searched, the impact remains empty.
The impact level is then weighted with the Test Case prioritization.
- Mandatory test: Impact Score * 1
- Optional test: Impact Score * 0,5
- No test: Impact Score * 0
If no prioritization is specified, the impact score is unchanged.
Based on the calculated impact score, the impact is categorized as follows:
| “n” is the impact score | Impact |
|---|---|
| 8 ≤ n | Serious |
| 6 ≤ n < 8 | Major |
| 4 ≤ n < 6 | Moderate |
| 2 ≤ n < 4 | Minor |
| 0 ≤ n < 2 | Insignificant |
The calculation is executed each time there is a change to content that is included in the calculation, e.g., changes to prioritization or changes for the folder of the Test Case.
Calculation of the likelihood
The calculation and analysis are only conducted for Test Cases where the likelihood slider is set to “Auto” and is based on Test Cases that are included in the same Version of the Project or Subproject.
From a business perspective, a complex feature would lead to complex Test Cases with a lot of information in the precondition and many test steps.
For the calculation, the median number of test steps and the median number of words in the preconditions are first determined for all Test Cases in one Version of the (Sub)Project. For each individual Test Case, the number of test steps as well as the number of words in the preconditions are compared with the corresponding median, and a value is assigned as a complexity factor:
| “f” is the corresponding complexity factor of a Test Case | Complexity level |
|---|---|
| 2 * Median < f | 5 |
| 1,2 * Median < f ≤ 2 * Median | 4 |
| 0,8 * Median < f ≤ 1,2 * Median | 3 |
| 0,5 * Median < f ≤ 0,8 * Median | 2 |
| 0 ≤ f ≤ 0,8 * Median | 1 |
The complexity “C” of a Test Case is then determined as the average of the previously calculated complexity values, from which the likelihood is derived.
| “C” is the average complexity | Likelihood |
|---|---|
| 4 < C | Almost certain |
| 3 < C ≤ 4 | Likely |
| 2 < C ≤ 3 | Possible |
| 1 < C ≤ 2 | Unlikely |
| 0 < C ≤ 1 | Rare |
| No value | No value |
AI keyword generation
This function is only available for project admins and system admins.
To generate keywords, a file (PDF or DOCX) must be uploaded in the “Risk-based testing” section.
Go to: My projects → Context menu (Sub)Project → Settings → “Risk-based testing” section → Edit → Generate keyword → File upload
There are several limits to the file:
- Type: PDF & DOCX
- Number of files: 1
- Max. file size: 15 MB
After the file has been successfully uploaded, the process can be started by clicking the “Process” button. If the generation was successful, a results table with the impact score and keywords is displayed in the details view. The identified industry, business context, and language are also displayed. Clicking on the "Replace current keywords" button closes the details view and the existing impact score table will be replaced by the new values.
If the generation is faulty, a corresponding message is displayed.
The uploaded file will not be saved, it will be deleted after one day at the latest.
User management
In this overview a list of all users is displayed. The IT administrators can create, edit, or remove user accounts.
Toolbar:
- “+ Users”: Create a new user account
- Search: Searches the list for the entered character string (min. 3 characters).
- Filter
Context menu:
- Delete
Only users that are not or were not assigned to a Q12-TMT business object, e.g., a Test Case in a closed Test Run, can be deleted.
Hint: If the Q12-TMT user management is used, the function “create” and “delete” are available. If the login is done via a user directory (e.g., AD, LDAP) or via single sign-on (SSO), these two functions are not available.
Create & edit
Mandatory information:
- User name
- Given name
- Family name
- System role
Each user can be assigned to one or more (Sub)Projects with different roles. It is also possible to set an expiration date for the account. Q12-TMT automatically sets users to “Inactive” as soon as the specified date has been reached. In addition, a user status can be manually changed between “Active” and “Inactive”.
Active users
The user admin sees a list of all active users in this menu. This list can be exported as a CSV file.
User roles and Permission
A system role is assigned to every user. It determines if a user is allowed to change the configuration.
System roles:
The admin is not assigned to a (Sub)Project.
Each user gets the “guest” role by default and should be assigned to at least one (Sub)Project. It is possible to assign different roles to a user in various (Sub)Projects.
(Sub)Project specific roles:
- Tester: Project members who create, maintain, and manage Test Suites and Test Cases; execute tests; document results; and generate reports.
- Test manager: Project members with all tester capabilities plus additional functions.
- Project admin: Project members with all test manager capabilities plus additional functions.
- Guest: Stakeholders who want to review the Test Case base, documentation, and execution status (e.g., participants from other Projects or management).
| User roles | Permission |
|---|---|
| Tester | Read-only access to the Project and Project Version pages. Create and edit Test Suites. Create, edit and delete Test Cases and folders. Print Test Cases as PDF. Create, edit and close Test Runs. Add, edit and remove Test Suites in Run and Test Cases in Run. Execute Test Cases in Run, document and edit test results. Create Test Run Report (PDF). Search for business objects. Print the search result list for Test Cases as PDF and transfer it to a Test Run. Pin and unpin business objects. Assignment as Assignee and Tester to a Test Case. Overview of assigned tasks. |
| Test manager | See tester, additionally: Edit Projects. Create, edit and close Versions. Delete Test Suite and empty Test Runs. |
| Project admin | See test manager, additionally: Create Subprojects. Change project settings. |
| Guest | Read-only access to the Project, Project Version, Test Suite, Test Case and Test Run pages. Print Test Cases as PDF. Create Test Run Report (PDF). Search for business objects. Print the search result list for Test Cases as PDF. Pin and unpin business objects. "My Task" page is not available. |