User Guide

Welcome to the mgm Q12-TMT User Guide.

This Guide is designed to empower both - newcomer and seasoned users - with the Q12-TMT features to streamline your testing processes. From setting up your project to creating reports of the test results, you will find all details of how the aspects of your test management are covered to ensure smooth operation and maximum effectiveness.

The User Guide is structured to give some short insights first for a quick start and then leads you through the main menu of Q12-TMT. For information about the administration settings, please have a look into the Administration documentation.

Let's bring your Test Management to the next level.

Getting Started

Login

Sign in to Q12-TMT with your username or your email address.

info

In order to use Q12-TMT, ensure you have an active user account and appropriate project permissions. To obtain these permissions, please request the administrator.

Wrong Password

If you enter a wrong password ten times in a row, you will be locked from trying again for a duration which increases further with each subsequent failed attempt.

To unlock your account, please reach out to the administrator.

Projects

Start by accessing the projects tree, which displays all accessible projects and subprojects.

Click on a project to enter, and you will be directed to the latest version of the (sub-)project.

info

If your project is not in the list, please contact the administrator to provide the corresponding permissions.

Navigation

After the selection of a project, Q12-TMT will initially show you the Test Suites list of the selected (sub)project. You can now navigate through the main menu on the left side.

1. Search: Search Test Cases and Test Suites
2. Pin board: List of all pinned objects in the project (Test Suites, Test Cases, etc.)
3. Project: Details about the currently selected project and version
4. Test Suites: List of all Test Suites in the project
5. Test Runs: List of all Test Runs in the project
6. My Tasks: All Test Cases the user is assigned to maintain or test
7. Risk Based Testing: Overview of the risk of all Test Cases in the project
8. Versions: All versions of the currently opened project

Search & Filter

Search

Q12-TMT provides a powerful search with the possibility to further filter your search results so that you can quickly locate Test Suites, Folders, Test Cases, Test Runs, Test Case in Run of the current project version.

To begin a search, click the Search icon in the left main menu.

Enter the string you want to search for. Select the type of object. Choose where to search. Click the “Search” button or press "Enter".

• Search: the string requires at least 3 characters. It can be a substring or multiple strings. The search is not case-sensitive.
  For example, searching for “log” returns content containing “log,” “login,” or “analogous".
  Searching with multiple strings like “check out” returns content with "check" and "out", but not content with only “check” or “out”.

• What: Select the type of object you are searching for: Test Suites, Folders, Test Cases, Test Runs, Test Cases in Run.

• Where: Choose the field to search in: "All fields", "ID", "Title", "Description", etc.
  For example, search for “C_189” in "Test Case" on "ID", or to find a Test Case associated with a specific requirement, search for the ticket number in “Test Case” on “All fields.”

In the search results, Q12-TMT lists all matching objects in the current project version.
You can further filter the results or directly work on them. For example, edit the first object, then the next, etc. or multiselect all results to pin them for later use, or print them.

Filter

As the search result list can become very extensive with larger project sizes, you can further filter the results based on various fields.
Click the Filter icon in the toolbar. Select the fields and field values, choose the operator ("Or" or "And"), and click "Apply".

• Filter Selector: Search or select the fields to filter on (based on the object in the search results): For example, filter Test Suites by tags.
• Filter Options: For each chosen filter, search or select values or "none". For example, tags: "Tag1" and "Tag2".
• Filter Operation: Where relevant, click the Operation icon and choose "Or" or "And".
  Then click the “Apply” button.
  

Practical Features

Profile

User Profile

Click on the User button in the top right corner to find your profile information and the logout.

The Profile provides information about your account.

• Avatar
• Given Name
• Family Name
• Username (unchangeable)
• Email (unchangeable)

You can edit them with a click on the "Edit" button in the toolbar.

Change Password

You can change your password in your user profile. To do so, follow the steps below:

1. Click on "Change password" in the Edit Mode
2. Stay logged in
3. You receive an email from Q12-TMT with a link
4. Click on the link to change you password
5. Log in with your new password

Projects & Roles

Users are assigned to roles that come with various privileges and permissions. To review your assigned roles, navigate to the "My projects & roles" section in your profile information.

info

To assign a user to a role, delete a user, or change the password of a user, administrative access rights are needed.

Shortcuts

Q12-TMT supports multiple keyboard and mouse controls. Besides "Ctrl/Cmd + S", which saves the current state of objects, Q12-TMT's shortcuts do not interfere with common browser controls.

Shortcut	Result
E	Enter edit mode of a form
Ctrl/Cmd + S	Save form
T	Create a Test Case in an opened Test Suite
F	Create a folder in an opened Test Suite
A	Enter / Exit the "arrange" mode of a Test Suite or Test Run
B	Toggle Bulk operations on/off
Ctrl/Cmd +	Open table/tree entry in new browser tab
	Open table/tree entry in new browser tab

Rich Text Editor

Input fields and Text boxes in Q12-TMT provide a variety of text formatting options, as well as the possibility to insert images and files.

This includes:

• italic and bold text
• strikethrough in text
• preformatted code blocks
• code spans
• links
• headers
• horizontal lines
• basic and advanced lists
• basic and advanced block quotes
• attachments like images
• tables

Formatting text is simplified by the distinction of two text box tabs:

• The Visual view presents the text as it is seen in Q12-TMT with all selected formatting options applied
• The Code view presents the plain text with the tags that produce the corresponding outcome of the visual view. It can be used to quickly format your text without the need of clicking a button.

If another user already edits an object in Q12-TMT, e.g. a Test Case, a message will appear in the top, informing the user that the object currently is locked. After applying the changes, the edit mode can be closed by clicking the Tab key.

Deep Linking

Q12-TMT saves Test Cases, Test Suites, and Test Runs in a hierarchical link structure using object IDs in the format

https://demo.q12-tmt.com/p/241/sp/_/v/1.0.0/s/9/c/17

This allows to reopen the same specific object from a different environment by copying the link. Additionally, this structure permits quick navigation among overviews of varying projects or versions, by simply replacing the corresponding number in the link. By this you can quickly switch between i.e. the latest version and older ones:

https://demo.q12-tmt.com/p/241/sp/_/v/latest/s/9/c/17

https://demo.q12-tmt.com/p/241/sp/_/v/2.1.0/s/9/c/17

Q12-TMT automatically creates links to Folders, Test Suites, Test Runs and Test Cases if the corresponding ID is written in square brackets (e.g. [C_2]). ID and title of the currently opened object, e.g. a Test Case, are displayed in the browser tab, simplifying the simultaneous usage of multiple tabs.

Pin Board

Test Cases, Test Suites and Test Runs can be pinned for quick access. This can be done by using the icon in the top right corner of objects.

In lists like the search results, the pin icon can be found at the end of each object row.

Click on the icon in the main menu to access all pinned objects. They are structured by their type. Open a category by clicking on it to get a list of all pinned objects of the corresponding type.

Metadata

Metadata are structured data that give basic information about objects (e.g. a Test Case). They are especially useful to filter certain sets of data, e.g. all Test Cases of a specific user or all Test Cases which have been executed in the past week.

Metadata exist for multiple objects in Q12-TMT, including:

• Projects
• Subprojects
• Test Suites
• Test Cases
• Test Runs

The metadata provide information about

• when the object was created or last edited
• by whom the object was created or edited
• IDs and version information
• in which Test Run the Test Suite has been executed
• additional information about the Project, Version, Test Suite, Test Case, etc.

Some contents depend on the type of the object, for example Test Cases contain metadata about its latest test execution.

Attachments

Attachments can be used to store files in a Project, Test Suite, Test Case or Test Run. The files can be added into text boxes, e.g. in a test step description, to enhance the text with an image.

To add files, navigate to the attachment section of your object (Project, Test Suite, Test Case, etc.) and click the button. You can now select one or more files from your local machine.

Alternatively, they can be directly inserted by drag and drop them into the marked attachment section.

Added attachments are listed below with a preview or type symbol and information about file name, upload date and the user responsible for the upload. The last column of the list gives an information whether the attachment is in use or not.

All columns of the attachment list are sortable by clicking on the corresponding header. At the end of each row you will find two icons to download and delete the file. Please note that attachments can only be removed in the Edit Mode.

Locking

To avoid conflicts concerning consistency, Q12-TMT locks Test Suites, Test Cases, etc., when working on them. Objects can only be edited, moved or (re)arranged by one user at a time. For all other users, these functions are locked in between. Deleting a locked object is also not possible.

Whenever an operation cannot be executed due to Test Cases being locked, an info message will appear at the top of the screen. Further information about the locking can be acquired by hovering the lock symbol.

Dashboard

The Dashboard is the first view that opens after logging in.

It contains user-specific links to all open Test Runs, all Tasks and specific Projects, as well as a link to the Project Overview. At the top, the Dashboard contains information about the state of the Project of the respective User.

The Dashboard also shows the amount of Defects in the Test Executions, counting them respective to their impact. Since users can link any kind of ticket to Defects, this count may not only display Bugs and Incidents but also any other kind of ticket.

It is possible to set a filter on the information TMT display in the Dashboard. The filter can be accessed from the Dashboard with the button on the top right. In the filter, selected projects and subprojects will appear on the Dashboard. Additionally, each project shows how many of its subprojects are selected versus the number of subprojects that are assigned to the user. By default, each project is displayed on the Dashboard.

Project

Overview

info

The following section shows how to use the projects tree as a tester or test manager, whereas creating a new project is only available with further access rights or in the role of a Q12-TMT administrator. If you were granted such permissions and want to create a new project, please have a look into the Administration documentation.

Projects are the main business objects to organize and manage your quality assurance work. They are the topmost hierarchical elements that structure subprojects, Test Suites and Test Runs.

Click on the icon in the top left corner to see the tree of projects that you are assigned to. The project tree will show you:

• Title and ID of Projects and Subprojects,

• number of included Test Suites

• number of current and total Test Runs

• button to navigate to the versions of the project

If you can't see a certain Project or button, ensure you have the required access rights.

Details

Select a Project to get the details. Initially, the list of all Test Suites will be shown.

Click on the button in the main menu to navigate to the project details. They contain the title and a description of the project, alongside all its attachments and metadata. You will also find the version-specific details.

To edit the project details, click on the "Edit" button in the toolbar. The only mandatory field is the project name.

Test Suites

A Test Suite is a collection of Test Cases and provides the hierarchical structuring of Test Cases. Test Suites can be added to Test Runs to execute the contained Test Cases.

Click on the icon in the main menu to get a list of all Test Suites in the current project version. Initially they are sorted alphabetically. Use the "Arrange" button in the toolbar to change this order.

To create a new Test Suite, click on the "+ Test Suite" button in the toolbar.

To delete or edit Test Suites, use the context menu on the right-hand side or right-click on the corresponding Test Suite. Only Test Suites that are not part of a Test Run and that are not locked can be deleted.

Each Test Suite is separated into three sections:

• Overview: A quick and basic overview of the Test Suite, consisting of the Test Suite title and description, internal parameters, corresponding metadata and all attachments. For each Test Suite a priority can be selected, which is initially set to "Medium".
• Test Cases: A tree of all Folders and Test Cases in the Test Suite. Test Cases can be added, removed, or edited from here.
• Related Test Runs: A list of all Test Runs that the Test Suite is a part of. Even Test Runs of other project versions are listed here.

When you select a Test Suite, Q12-TMT will automatically navigate to the Test Cases section.

Overview

The overview of Test Suite displays the name, ID, description, and priority. Additionally, attachments can be added to the Test Suite in this section. Tags may also be assigned to a Test Suite, enabling the filtering of Test Suites based on these Tags and facilitating efficient navigation.

The section "Internal" lets the user set time booking information about the Test Suite.

Test Cases

A Test Case is a set of activities (test steps) in a system that intends to verify whether the software runs correctly and whether all requirements are met.

Tree

The Test Cases tree groups all the Test Cases which belong to a certain Test Suite. To achieve a hierarchical structure, folders can be used to represent different scenarios.

Create folders with the "+ Folder" button in the toolbar or by directly inserting them into the appropriate parent folder via context menu. A description can be added to the folder as well.

You can create Test Cases in the same way using the "+ Test Case" button in the toolbar or in the context menu.

To insert Test Cases into their correct locations, it may be necessary to move them. The "Arrange" button allows moving Test Cases and folders via drag and drop. This works for multiple entities at once. You can also arrange Test Cases by right-clicking the desired Test Case or with the context menu on the right-hand side. Select "Copy" or "Move" and paste it into the target location. These options additionally allow the movement and copying of Test Cases to locations outside the current Test Suite. Be aware: Test Cases that currently are a part of an open Test Run cannot be moved to a different Test Suite.

With the button for bulk operations in the toolbar, you can select multiple Test Cases to move/copy them or to set/remove certain parameters for all of them at once.

The path to a Test Case can also be seen at the top of the Test Case Overview.

Create & Edit

When creating a new Test Case, it is mandatory to enter a title. A Test Case can be saved and edited afterward. The system will automatically create a unique ID and the metadata of the creation, as soon as the Test Case is saved.

Editing a Test Case will lock the Test Case for other users.

Details

Click on a Test Case to get the details. In the details of a Test Case it is possible to print out a Test Case into a single PDF. The resulting file will contain all data of the Test Case, except for its metadata, its attachments, and its general information, e.g. status, type, or automation. The print includes the date and time when it was created.

Additionally, you can copy, move or delete a Test Case via the respective buttons in the toolbar. To move or copy more than one Test Case, bulk operations can be used.

Use the "Edit" button to start the Edit Mode. You can now set the Status and an Assignee. Only users with access rights in the project can be selected. You can select more attributes from additional drop-down fields: Type of the Test Case, its Prioritization, the current Automation Status and the Estimated execution time.

Further sections to maintain are:

• Description: Text box to describe the aim of the Test Case
• Sources: The sources where the Test Case has been derived from (either a ticket or a document)
• Criteria: Basic parameters which have to be met (e.g. dependencies or browser versions)
• Risk: Assessment of the likelihood and impact of errors and problems
• Attachments: Files can be uploaded here (e.g. a diagram or target state screenshot). Uploaded images can be added to a description or to a test step. Attachments can be downloaded on any device from here.
• Preconditions: Shows the circumstances and necessary settings which are required to run the Test Case
• Test Steps: Collection of small, ordered, and indivisible steps, each consisting of an action and an expected result. When executed in the given order, they make up the whole Test Case. When an error occurs it can be tracked down to the specific test step during which the error occurred

Version Delta

The Version Delta helps to identify Test Cases that were added or changed in the current version. With the help of the Version Delta, new and changed Test Cases of the current version can be quickly detected and selected for a Test Run or for documentation purposes.

When a new Test Case is added or an existing Test Case is edited, the Version Delta is automatically set to "yes" by default. It can be set to "yes" and "no" manually as well.

The colors help to quickly identify the value (yes=blue, no=grey). To switch it on or off, simply click on the button below the "Version delta" heading.

When searching for Test Cases, either via Search or inside a Test Run via the Smart Selection, Test Cases can be filtered for their Version Delta. This way it is possible to automatically filter for new or changed Test Cases when selecting Test Cases for a Test Run and therefore focus on features that are new or were adapted in comparison to the previous version.

Tickets

Q12-TMT can link issues directly from external ticket frameworks. This can be used to link a ticket as the source of a Test Case, e.g. User Story.

Syntax-wise, type the name of the issue you want to include. Q12-TMT will automatically recognize the object and link the correct issue.

Tenant Admins can integrate instances of Azure DevOps or JIRA into TMT, while project admins can add them to their (sub-)projects.

Tags

Tags can be found in the criteria section of the Test Case. They can be used to provide related information, e.g. whether the Test Case relies on customer data or whether there is a related incident. There is no limit of tags that can be added per Test Case. In order to support consistency, added tags are saved for the whole project and all subprojects and can be assigned to multiple Test Cases. Tags are not case-sensitive and limited to a maximum of 30 characters. Whitespaces are not allowed.

Test Steps

Test steps separate the Test Case into smaller tasks which are executed successively and each consist of an action and an expected result. Use the text boxes to describe them in any detail. Each Test step can later be marked with a test result separately.

More Test steps can be added with the "Add" button below. The two arrows next to the Test steps allow to rearrange the order of the Test steps. The context menu lets you insert a new test step above or below as well or copy/delete the test step.

The position of Test Steps can be changed with Drag & Drop.

History

The history of every Test Case can be accessed through the icon in the toolbar of the Test Case. It includes every change the Test Case underwent in chronological order, starting with the creation.

Every entry in the History contains the corresponding metadata, e.g. the user who triggered the entry by creating or editing a Test Case, the exact date, time, and version number.

Every time a Test Case is edited, the original, as well as the new content, is saved for every changed field. To make the changes more obvious, colors are used to supplement the Test Case history. Green entries stand for new additions, red entries stand for deleted passages.

Related Test Runs

The "Related Test Runs" section lists all Test Runs the Test Suite is part of. You can select a Test Run to directly navigate to it.

Test Runs

To execute Test Cases, the corresponding Test Suite must be added to a Test Run. It is possible to include more than one Test Suite in a Test Run, and to exclude certain Test Cases from the Test Run.

Thus, Test Runs are highly configurable sets of Test Cases that are executed together. Each Test Run refers to a single execution and can only have one result. If you want to re-execute the same set of Test Cases again, you can do so by copying the Test Run.

Click on the icon in the main menu to get a list of all Test Runs of the current project version.

The Test Run menu presents a list of all currently existing Test Runs of the project. There is information about the Test Runs states, as well as the relative percentage of how many Test Cases are or have been executed and detailed information about the test results.

To delete or edit Test Runs, use the context menu on the right-hand side or right-click on the corresponding Test Run. Please note: Only empty Test Runs that not even contain a single Test Suite can be deleted.

Create & Edit

In the Test Run list, you can create a new Test Run using the "+ Test Run" button in the toolbar. The title of the Test Run is mandatory, the description and configuration are optional. A new Test Run is in the State "open" by default.

The newly created Test Run will appear in the list and can be edited afterward.

Assign Testers

Testers can either be assigned to a specific Test Case or they can be assigned to multiple Test Cases, Test Suites, or even to whole Test Runs.

Click on the button for bulk operations to assign Testers to one or several Test Runs. It is also possible to assign multiple testers to a Test Run.

Alternatively, the same procedure can be done with the Test Suites within the Test Run or with the Test Cases within the Test Suites that are part of a Test Run. To quickly add testers to Test Cases from different Test Suites within a Test Run, use the feature in the Test Scope section.

info

When assigning a tester, an email will be sent automatically to the corresponding user. Only users that have access rights in the current project can be assigned.

Overview

Select the Test Run for the details. The Overview section presents all existing results, the number of Test Cases and how many of them already have been executed, as well as the corresponding Attachments and Metadata. Use the "Edit" button in the toolbar to edit the input fields, add Attachments or change the state of the Test Run.

Test Selection

The Test selection section presents a list of all Test Suites which are currently assigned to the Test Run. If the Test Run just has been created, this list will be empty. To add new Test Suites, click on the "+ Test Suite" button in the toolbar. You can select any of the Test Suites of the current project version.

The "Arrange" button allows changing the order of Test Suites by drag and drop. This works for multiple entities at once.

To quickly change the corresponding tester of multiple Test Suites, more than one Test Suite can be selected with the button for bulk operations.

After adding a Test Suite none of its Test Cases will be part of the Test Run by default. To select Test Cases, click on the Test Suite. The Test Suite details will show the full Test Cases tree which is already included in the Test Run. Initially it will be empty. To add or remove certain Folders or Test Cases, click on the "Manage" button and select or deselect the branches of the tree which shall be included or excluded. This process is further simplified with the "Smart Select" feature that allows to automatically select or deselect Test Cases that fit certain characteristics. To use smart-select, click on the corresponding button in the toolbar while managing the Test Cases. The Smart Select feature can be navigated with the mouse or via the TAB key. ENTER can be used to click on items and the modal can be closed again by pressing ESC. It is possible to filter according to Risk Based Testing parameters within the Smart Selection.

In the Test Case tree of the Test selection, use the button at the end of the row of a corresponding Test Case to execute it.

You can select a Test Case to see its details. In the Test Case details, there is another way to execute it with click on the "Execute Test" button in the toolbar. For more information about executing Test Cases, see Test Execution.

Test Cases in a Test Run are read-only copies of the Test Cases in the Test Suites menu. To change them, use the "Show Original" button in the toolbar of the Test Case details. This button links the original Test Case in the Test Suites menu to edit it. The derived Test Case in the Test Run will automatically update.

Test Scope

In the Test Scope section, all added Test Cases of the Test Run are shown in a flat list.

From this list, Test Cases can be executed directly with click on the button, or selected to see the Test case details.

To set test execution results for one or more Test Cases directly, use the button for bulk operations in the toolbar.

Test Execution

When executing a Test Case, you can map an individual tester with the drop-down field just below the title. Secondly, there are the test steps, which can get an optional result. Use the button on the right-hand side of each step to mark them as passed with a single click. A custom result can be entered with a click on the button next to the prior one. When a custom result is attached, an information icon will appear next to the test step result, showing the content by hovering over it. Thus, errors can be located very quickly, and they can be backed by useful information, e.g. the error message.

In the last section "Overall test result", you can find the Result dropdown which is mandatory and contains the value "Untested" by default. Select the appropriate result of the test execution. In case of any errors or other noteworthy incidents appeared during the execution, there are two more input fields to document Defects and Result details.

It is not necessary to maintain test step results to set the Overall result.

Afterward the Test Case Results can be saved. By using the "Save & Next" button, the Results will be saved and the next Test Case will be opened for execution automatically.

Test Execution History

Similar to the Test Case history, there is a history for Test Cases in Runs. It lists all edits of the test execution, as well as all edits of the original Test Case, giving information about whether the last execution has happened in the most actual state.

Create Report

Q12-TMT provides reports for Test Runs. To create a report, select a Test Run and click on the "Generate Report" button.

This function will create a PDF that contains the name, state, and description of the Test Run, as well as a list of all included Test Cases alongside their IDs and results. It incorporates the absolute amount of executed Test Cases, as well as the corresponding relative percentage.

When generating a report, an info wizard will appear, notifying the user that the report is currently generating. When the generation is done, the report can be downloaded.

info

Reports are available in German and English language. The language can be set with further access rights in the system configuration. Please have a look into the Administration Guide to do so.

My Tasks

Whenever you are assigned to a Test Case, Q12-TMT will automatically inform you via email. You can either be assigned to a Test Case in a Test Suite or you can be assigned as a tester to a Test Case in a Test Run. Both assignments will be listed in "My tasks", as long as the Test Cases are not in a final status.

Click the icon in the main menu to get an overview. The tasks are structured by their type. Open a category by clicking on it to get a list of all your tasks of the corresponding type.

Risk Based Testing

Since it can be difficult to assess, which Test Cases are especially critical, Q12-TMT features Risk Based Testing.

Click on the icon in the main menu to access it.

There are three risk layers within the Risk-based Testing menu:

• Business Logic
• Test History
• Heatmap

Business Logic

Q12-TMT assesses the risk, by considering the likelihood of an error occurring in the current Test Case, as well as the impact an error would have. When hovering over the fields of the pie chart, Q12-TMT will list all combinations of likelihood and impact that fit in the corresponding risk section and the amount of Test Cases that belong to each combination respectively.

Use the "Show Cases" button to navigate directly to the corresponding Test Cases.

With the Smart Select feature, Test Cases can be selected by their respective risk.

In the overview it is possible to show all test cases with a particular risk assessment, as well as to create corresponding Test Runs.

Test History

Q12-TMT assesses the risk of a Test Case also with its Test History. This includes the frequency of failed executions in the past across all versions.

The severity of those failures is estimated by analyzing the priority of the linked Defects of failed executions.

Release Scope

The Release Scope assesses risks by analyzing the software release that is under test. This is achieved by assessing linked tickets. In the case of source tickets, the TMT Release Version and Jira Fix Version of the ticket are compared. If the versions match, the ticket is a Feature Test. Feature Tests are treated with high or medium risk, depending on the priority of the ticket.

If the Test Case has Defects that are linked in an open or closed Test Run, TMT will treat it as a Defect Retest with risk assessment reaching from high to low.

If a tag exists in a Test Case that also exists in a Feature Test or Defect Retest, the Test Case becomes automatically part of a regression test.

For every other Test Case that doesn't fit one of the above criteria, the risk is either undefined in the case of enabled Version Delta, or TMT assigns it a low risk in the case of disabled Version Delta.

Heatmap

The Heatmap is a combination of all other layers. The risk shown in the Heatmap corresponds to the highest risk assessment attained by any Test Case within any of the individual layers.

The diagram shows the risk assessments for all Test Suites. The corresponding Test Suite and an overview of the involved Test Cases can be highlighted by hovering over the Heatmap entries or navigating to them via keyboard.

Versions

Project versioning is one of the key features to organize your projects and testing processes.

Click on the icon in the main menu to get a list of all subprojects and project versions. The subproject or version can be changed by clicking on the corresponding object.

When creating a new version, it is possible to enter descriptive information like the name, version number or key points. Information about the context of the current Release can be entered in the Release Version field, mapping to the corresponding Test Cases.

info

New versions can only be created with further access rights. Please have a look into the Administration documentation to do so.

Privacy & Legal Terms

The Privacy Policy and Terms & Conditions of TMT can be looked up in the About section of TMT.

When clicking on the button, a dropdown menu will appear. The legal notes and terms and conditions are linked at the bottom of this menu.

By default, all information is displayed in English. The language can be switched to German.

Administrative Features

User Admin

The User Admin can create, edit and delete Users, as well as their respective roles and the corresponding access rights.

It is possible to use User Directories to manage accounts but there is also a built-in standalone management tool within TMT.

A User Admin is also able to activate or deactivate accounts.

User Management, Role Management and Access Rights Management can be accessed via the hamburger icon in the top left corner.

In the User Management a User Admin can edit accounts. Alongside the password it is possible to set an expiration date to accounts. TMT will automatically set the user to "Inactive" when the date ist reached. A User Admin can also assign system specific or project specific roles.

The "GUEST" role is automatically assigned to user accounts without any roles.

Project Admin

The Project Admin Role has to be assigned to a specific Project. Users who obtain this role can customize Table Columns for Test Suites and Test Runs from the Project Overview.

By ticking the desired fields, they will appear as column heads in the respective view of the Test Suite or Test Run.

Tenant Admin

The Tenant Admin is able to oversee and export data of the tenant, namely the list of Active users.

The list of Active users can be accessed via the hamburger icon by selecting "Active users" .

By clicking "EXPORT USER DATA", this list will be exported as .csv file.

In the same hamburger menu, the tenant can be configured via the "Tenant settings".