User Guide

Welcome to the mgm Q12-TMT User Guide.

This guide covers Q12-TMT features for new and experienced users. It starts with a quick-start overview, then walks through the main menu, from setting up a project to creating test result reports.

For information about administration settings, see the administration documentation. This guide addresses the “Tester” role. Features requiring higher permissions or specific user roles are marked with an Info box.

note

See our video tutorials on the Q12-TMT YouTube channel.

Getting Started

Login

To use Q12-TMT, an active user account with the appropriate project permissions is required. Permissions are assigned by the user administrator. For further information see the administrator guide.

Log in to Q12-TMT with a username or email address.

After too many incorrect login attempts, Q12-TMT locks the account for the configured period.

	Use of Q12-TMT´s internal user management	Use of a directory service (e.g., AD, LDAP) or single sign on (SSO)
Reset password	If the password is forgotten, the user administrator can set a new password.	Contact the company's IT administration to reset the password.
Wrong Password	After 10 incorrect attempts, Q12-TMT permanently locks the account. Contact the user administrator to unlock it.	Company policies govern the number of failed login attempts and the lockout period. Contact the company's IT administration to unlock accounts.

Help and About

Click the Help button to open a dropdown menu with the user manual and guided tour. Click the Info button to access version information, report issues, and open the release notes, user terms, legal notice, and privacy policy.

Guided Tour

The guided tour starts automatically on the first login. The tour is an interactive walkthrough of the main features in Q12-TMT. To restart the tour, click “Start Tour”.

Profile

User Profile

Click the User button at the top right to view profile information and log out.

The Profile provides information about the account.

• Avatar
• Given Name
• Family Name
• Username (unchangeable)
• Email (unchangeable)
• Assigned projects and roles (unchangeable)
• Language setting

Click the edit button in the toolbar to edit the information.

Change Password

info

The password change function is available with Q12-TMT's internal user management. For logins via a user directory (e.g. AD, LDAP) or single sign-on, password changes are managed externally.

Use of Q12-TMT´s internal user management	Use of a directory service (e.g., AD, LDAP) or single sign on (SSO)
The password change is completed in several steps: 1. In edit mode, click “Change password”. 2. Close the notification and log out. 3. Click the link in the email sent by Q12-TMT. 4. Log in with the current credentials. A password change form appears. 5. Enter the new password and confirm it. 6. After confirming, Q12-TMT will log out the user automatically. 7. Log in with the new password.	Contact the company's IT administration to change the password.

Projects & Roles

Roles define privileges and permissions. Assigned roles can be reviewed in the “My Projects & Roles” section of the profile.

For more information on permissions see chapter “Permission”.

Projects

Up to five Projects assigned to the user are displayed on the dashboard. Click a project tile to open the Test Suites overview in a new tab. The most recent Version opens by default. Information on displaying and changing Projects can be found in the “Dashboard” chapter.

The project structure lists all Projects and Subprojects assigned to the user. It can be opened via “My Projects” in the main menu or the “My Projects” button on the dashboard. From there, navigation to any Project, Subproject, or Version is possible.

info

If the Project is not in the list, contact the user administrator to grant permissions.

Navigation

After selecting a (Sub)Project, Q12-TMT displays the Test Suites list. Use the left sidebar to navigate further.

• Search: Search Test Cases, Folder, Test Suites, Test Case in Run and Test Runs.
• Pin board: List of all pinned objects in the Project (Test Suites, Test Cases, etc.).
• Project: Details about the currently selected Project and Version.
• Test Suites: List of all Test Suites in the Project.
• Test Runs: List of all Test Runs in the Project.
• My Tasks: All Test Cases the user is assigned to maintain or test.
• Risk Based Testing: Overview of the risk of all Test Cases in the Project.
• Versions: All Versions of the currently opened Project.
• Test automation: Overview of the test automation status of all Test Cases in the Project.

Practical Features

Tickets

In Q12-TMT, external ticket systems such as Azure DevOps or Jira can be linked:

• A Test Case links to a requirement or story ticket via the “Source Tickets” field.
• A Test Case in Run links to bug or incident ticket via the “Defect” field.

To link an issue, enter the ticket key. Q12-TMT recognizes the key and displays the ticket information on hover. Q12-TMT fetches the ticket data every hour.

info

Ticket linking requires a configured ticket system instance (e.g. Atlassian Jira or Azure DevOps). The tenant administrator configures this in Q12-TMT.

Status change and impact

Assign different statuses to Versions, Test Cases (Test Case status and test automation), and Test Runs. Status changes to a Version or Test Run affect other business objects and calculations.

Change the status of a Version
A Version has the status “Open” or “Closed”.

In an open Version, all business objects (Test Suite, Test Case, or Test Run) of the (Sub)Project can be created, edited, or deleted.
When the status is set to “Closed”, all saved states are frozen. The Version is in read-only mode. For more information, see chapter “Versions”.

Change the status of a Test Case
The Test Case status is independent of other objects, calculations, and processes. It appears in various views and serves as a workflow too.

A Test Case assigned to a user with a status other than “Completed” appears in the “My Tasks” section. Setting the status to “Completed” removes it from this section.

Change the status of a Test Run
A Test Run has the status “Open”, “In Progress”, or “Closed”.

Setting the status to “In Progress” freezes the risk values of the Test Cases within the Test Run. These values feed into the risk burndown diagramm. Adding and removing Test Suites and Test Cases is still possible.
Setting the status to “Closed” freezes all saved states. The Test Run is in read-only mode. For more information, see chapter “Test Run – Overview”.

info

Changing the status of a Version and a Test Run requires the test manager or project administrator role.

warning

Closing a Version is irreversible.

Shortcuts

Q12-TMT supports keyboard and mouse shortcuts. Q12-TMT shortcuts are compatible with common browser controls. The exception is “Ctrl/Cmd + S”, which saves the current state of objects.

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
J	Opens the next Test Case, a Test Suite or Test Run, in the detailed view
K	Opens the previous Test Case, a Test Suite or Test Run, in the detailed view
Tab / Shift + Tab	Navigates through Q12-TMT
↑ , ↓	Navigates through lists and sidebar
Enter	Open and close a function in the toolbar Open objects, e.g. Test Case in a list activates sortable table headers
Space	Open and close a function in the toolbar Checkboxes can be de- and activated
Esc	Close a modal
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 support text formatting options, images insertion and files attachments.

The text formatting options include:

• italic and bold text
• strikethrough text
• text colors
• horizontal lines
• blockquote
• ordered and unordered lists
• indentation and outdentation of lines
• tables
• insert an attachment from the “Attachments” area
• insert graphics as a file or URL
• links
• code spans

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 displays the plain text as markup code, producing the corresponding output shown in the Visual view. This view can be used to format text quickly without using the toolbar buttons.

Deep Linking

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

https://[tenant-subdomain].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://[tenant-subdomain].q12-tmt.com/p/241/sp/_/v/latest/s/9/c/17

https://[tenant-subdomain].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.

Filter

In large Projects, lists can grow. The filter narrows entries to locate specific object. Click the filter icon in the toolbar to open the filter panel. For some lists, filters are already available directly in the toolbar.

The filter panel consists of the following areas:

• Filter selector: The available selectors vary depending on the list. Filters present in the toolbar are preselected and inactive. Combine one or more selectors as needed.
• Filter options: Depending on the selected selector, an input field, checkboxes, or radio buttons appear. Checkboxes support multiple selections.

Where applicable, the operation icon defines whether filters are combine with “Or” or “And” logic. Click “Apply” to close the panel and filter the list. Active filter selectors appear in a filter bar above the list. Click a selector to adjust its options, or click the x icon to remove it.

Empty selectors are ignored when filtering results.

Bulk operation

Bulk operations are available for many lists and allow multiple objects to be edited at once, for example assigning Test Cases. Where available, this is noted in the relevant chapter.

Click the Bulk Operation icon to activate. Click the icon again to close it.

Activating the bulk operation displays checkboxes for selecting individual objects. Click the checkbox in the column header to select or deselect all objects.

Once one or more checkboxes are selected, a number next to the icon shows how many rows are selected. A dropdown next to it lists the fields available for editing. After selecting a field, a second dropdown opens to choose the value to apply. For some fields, click Remove to clear the field, or click Set to confirm the selection.

On some pages, additional action buttons (e.g. Copy) appear next to the dropdown.

Clicking an individual button, “Set”, or “Remove” starts a background process. A message in the top right area confirms the start and end of the process. Locked objects are skipped, and Q12-TMT displays a message listing them.

Arrange

By default, all lists are sorted alphanumerically. The Arrange function sets a custom order, which replaces the default sorting. New objects appear at the end of the list and are sorted manually. The order in Test Suites can be reset to default.

Arrange Test Cases, folders, and suites at any time. Changes apply to open Test Runs as well. Click the Arrange button to enter the arranging mode.

Move objects within the list using drag and drop or cut and paste. Cut applies to single objects. To move several objects at once, use Bulk operation with drag and drop. To move objects across pages, use cut and paste.

Move Test Cases to another folder, or position them above or below it. Press Esc or click Cancel to cancel a cut. Click Exit arranging to save changes and close the mode Open another page to save and close the mode.

Attachments

Upload documents and images and attach them to Projects, Versions, Test Suites, Test Cases, and Test Runs. Insert files into certain text fields with the Rich Text Editor, for example in Descriptions, Preconditions, Test Steps, and Result details. Upload files in the “Attachment” section of the business object to reference them in a rich-text editor field.

Rich-Text Editor
Click “Insert Attachment” to reference a file already added to the attachments section.
Click “Insert Image” to select an image from the computer. The image will also be listed in the attachments section.
In the rich-text editor images are displayed in a reduced size and the other files are referenced with a link on the file name.

Attachments section
Attachments are listed in the table with a preview (for images) or a type icon, along with information about the file name, upload date, and the user responsible for the upload. The “Referenced” column indicates whether the attachment is referenced in a text field. Sort any column in the attachment list by clicking on the corresponding header.

For each file, the following features are available in the attachments section:
In view mode

• image preview: Open the image in a preview.
• download: Save the file to the device.

In edit mode

• image preview: Open the image in preview.
• download: Saves the file to the device.
• delete: Delete the file from the business object of the selected Version.
• upload: Open a window to select and upload one or more files from the local computer.

Files can also be dragged and dropped directly into the designated attachment area.

Attachment limits:

• Max. file size: 5 MB
• Max. size of all files: 100 MB
• Max. amount of files: 100

Locking

Q12-TMT locks Test Suites, Test Cases, and other objects during editing. Only one user can edit, move, rearrange or delete an object per browser tab. Q12-TMT also locks these function for background processes such as individual functions or bulk operation.

If an operation cannot be completed because the Test Cases are locked, Q12-TMT displays an info message at the top of the screen. Additional details about the lock can be viewed by hovering the lock symbol.

The lock expires after 120 minutes of inactivity. A notification message appears 15 minutes before it expires.

Metadata

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

Q12-TMT supports metadata for the following objects:

• Projects
• Subprojects
• Test Suites
• Test Cases
• Test Runs to a ticket system, e.g. Atlassian Jira or Azure DevOps, is configured and access is permitted, the ticket area appears.

The metadata provides information about:

• When the object was created or last edited
• Who created or edited the object
• Version information
• Last test execution of a Test Case

Dashboard

The Dashboard is the first view that opens after login. Click the Q12-TMT logo, or the “Dashboard” section in the main menu, to reopen it.

The guided tour starts automatically on first login.

Q12-TMT displays user-specific information on the Dashboard, depending on the selected Projects, Subprojects, and their Versions.
This includes:

• Key Performance Indicators: Task status, Test Run progress, and assignments.
• Project tiles: Selected Projects, Subprojects and their Version, and “My Projects” button.
• Test Runs: All Test Runs with visualized progress.
• Defects: A chart with stored tickets with their priority.
• My Tasks: A list of assigned Test Cases and Test Cases in Run.

info

If the connection to a ticket system, e.g. Atlassian Jira or Azure DevOps, is configured and access is permitted, the ticket area appears.

Key performance indicators

No Assignee: Number of Test Cases without an assignee, except Test Cases with status “Done”.
No Tester: Number of Test Cases in Run without a tester, except already executed Test Cases in Run (overall result “Passed” or “Failed”).
Test Runs: Number of all Test Runs.
Test Cases: Number of Test Cases in Run of all Test Runs.

Untested: Number of Test Cases in Run with status “Untested” across all Test Runs, and their percentage of the total Test Cases, rounded to the nearest whole number.
In Execution: Number of Test Cases in Run currently in execution (overall result not “Untested”, “Passed” or “Failed”), and their percentage of “Test Cases”, rounded to the nearest whole number.
Executed: Number of Test Cases in Run already executed (overall result “Passed” or “Failed”), and their percentage of “Test Cases”, rounded to the nearest whole number.

Assignee: Number of Test Cases with status other than “Done”, currently assigned to the user.
Tester: Number of Test Cases in Run with overall result other than “Passed” or “Failed”, currently assigned to the user as tester.

Project tiles

The Dashboard displays a tile for each selected Project or Subproject, showing the title, the number of possible Subprojects, and the selected Version.

Click a Project tile to open the Test Suite overview for the selected Version in a new tab.

If only Subprojects are selected, the tile displays the Subproject title. If 2 or more Projects are selected, the tile does not list Subprojects separately. On small screens, the Dashboard shows 2 Projects. On larger screens, up to 4 or 5 Projects appear, next to the “My Projects” button.

Click the My Projects button to open a list of all Projects and Subprojects assigned to the user, in a new tab. For more information, see chapter “Project”.

Click the Projects button above the Key Performance Indicators to open the filter.

The filter lists all Projects and Subprojects assigned to the user. Select or deselect them using the checkbox at the start of the row. The filter displays the selected Version after the (Sub)Project title. Click the version icon at the end of the row to open a list of all Versions of the (Sub)Project. The icon appears only for selected (Sub)Projects.

Select a specific Version, or select “Always the latest” to always display the latest Version for assigned or created (Sub)Projects.

Test Runs

Q12-TMT displays all Test Runs of the selected Projects and Versions, with status “Open”, “In Progress”, or “Closed”. Below each run name, a horizontal progress bar indicates the current test progress.
Open a single Test Runs in a separate tab, or click the link at the end of the list to open a list of all Test Runs.

Defect

The chart shows the sum of valid tickets, store in the “Defects” field during test execution. The size of each segment is proportional to the number of defects of the respective priority. Q12-TMT retrieves the priority from the connection ticket system and groups tickets into 4 classifications. Q12-TMT treats all ticket types equally (bugs and requirements).

Click the link at the end of the section to open a list of all tickets. This list shows the type, key, priority, summary, status, and related Test Cases in the run for each stored ticket.

Q12-TMT Classification	Jira Ticket priority
“Blocker”	Blocker
“Critical”	Critical and Highest
“Major”	Major and High
“Normal und below”	Medium, Normal, Low and Minor

My Task

Q12-TMT displays a list of Test Cases and Test Cases in Run assigned to the user as an Assignee or as a Tester, across all selected Projects, Subprojects and Versions. Click the link at the bottom of the list to view all Test Cases.

• Assignee: Tst Cases without status “Done” appear.
• Tester: Test Cases with a result other than “Passed” or “Failed” appear. Only Test Cases from Test Runs that are not closed appear.

Click a Test Case to open it in a separate tab.

Search

Q12-TMT provides a search function with additional filters to locate Test Suites, folders, Test Cases, Test Runs, Test Case in Run of the currently selected Version.

To begin a search, click the Search icon in the sidebar.
Enter the search string and select the target business object and the search scope. Click on “Search” or pressing Enter to begin the search.

Search request

Input field

• Minimum length: 3 characters (exception: ID field 2 characters).
• Multiple search terms are interpreted as an AND condition.
• Case-insensitive.

For example, searching for “log” returns content containing “log”, “login”, or “analogous”.
A search with multiple terms like “check out” returns results containing both “check” and “out”.

What? (search object)

• Radio buttons to select the object type
• Options: Test Case, Test Suite, Folder, Test Case in Run, and Test Run

Where? (search scope)

• Dropdown to select the scope/fields to be searched.
• Available fields depend on the selected object. Search object and selectable search scope

Search object	Search scope (drop down)
Test Case	All fields, title and ID
Folder	All fields, title, ID and description
Test Suite	All fields, title, ID and description
Test Case in Run	All fields, title, ID and overall result details
Test Run	All fields, title, ID and description

tip

Use cases

• Search for a specific Test Case: Enter “C_189”, business object “Test Case”, search scope “ID”.
• Find all Test Cases linked to a specific ticket: Enter the “ticket number”, business object “Test Case”, search scope “In all fields”.

Search result

In the search results, Q12-TMT lists all matching objects in the selected Version. If no results are found, a message appears in the empty results list. Depending on the selected object of search, different additional functions are available. All functions are described below.

Toolbar:

• print: Create a PDF of the search results list.
• create run: Create a Test Run with all listed Test Cases. The title of the Test Run is filled automatically and contains the searched string.
• bulk operation: Pin or edit specific parameters all at once.
• filter: Access the filter mask to filter the search results list.

Filter bar:

• Test Suite: Narrow the listing to the selected Test Suite.
• Assignee: Narrow the listing to the selected assignee.
• Tester: Narrow the listing to the selected tester.
• Result: Narrow the listing to the selected test result.
• List of all other filters used.

For each selectable search result at the end of a row (incl. context menu):

• edit: Open the object in edit mode.
• execute test: Open the Test Case in Run in execution mode.
• open in new tab: Open the object in a new tab.
• pin object: Pin the object for later use through the pin board.
• print: Create a PDF.

Open the context menu by clicking the three dots at the end of the line, or by right-clicking the row. Some functions are temporarily locked when another user is editing.

Function /Search object	Test Case	Folder	Test Suite	Test Case in Run	Test Run
Filter	✓	✓	✓	✓	✓
Edit	✓	✓	✓	X	✓
Pin	✓	X	✓	✓	✓
Open in new Tab	✓	✓	✓	✓	✓
Print	✓	X	X	✓	X
Execute Test	X	X	X	✓	X
Bulk operation	✓ (Assignee, status, pin)	X	✓ (pin)	✓ (Tester, overall result, pin)	✓ (pin)

The “Create run” button is available in the search result list of Test Cases. Click to create a new Test Run with all Test Cases of the (filtered) result list. A notification in the top right area indicates when the background process starts and ends.

Pin Board

Information about “Pin Board” from 1:20

Test Cases, Test Suites, Test Runs, and Test Cases from Test Runs can be pinned for quick access. Objects are pinned using the pin icon in the top right corner of an object or at the end of the row in list views.

The number of pinned objects is displayed next to the pin icon in the sidebar. Click the icon in the sidebar to open an overview of the four object types.
The number of pinned objects per category is shown below each button. If no object is pinned for a category, it is disabled.

A list of all pinned objects of the corresponding type opens by clicking the respective button. From this overview, individual objects can be opened in read or edit mode, or removed from the pinboard. Additional options in the context menu allow objects to be opened in a separate tab or printed as a PDF.

Click “Remove all from pinboard” to remove all objects of a category at once.

Project

Overview

info

Creating a new Project requires the IT administrator role. For details, see the Administration Guide.

Projects are the main business objects for organizing and managing quality assurance work. As the top level elements, they structure (Sub)Projects, Test Suites and Test Runs.

The project structure lists all assigned Projects and Subprojects. Open it via “My Projects” in the main menu or the “My Projects” button on the dashboard. The tree structure expands and collapses per (Sub)Project, or for all at once using the button on the right in the top right.

The following functions are available depending on permissions:

• Create a new Project
• Create a new Subproject
• View Versions
• Edit existing Projects or Subprojects
• Adjust settings for Projects or Subprojects

Details

Select a Project to get the details. By default, Q12-TMT displays the Test Suites list. Click on the button in the sidebar to navigate to the project details.

The display is divided into the following sections:

• general with Title, ID and the description of the Project
• attachments of (Sub)Project
• version
• attachments of version
• metadata

The attachments of the (Sub)Project are taken over when a new Version is created.

The “Version” section contains version-specific details entered during the creation. A pie chart shows the total number of Test Cases and the proportional share per status (e.g. “In progress” or “Done”).

To determine the risk values for the “Release Scope” category, the stored release version should match the software release to be tested and should match the Fix Version maintained in the ticket system, e.g. Atlassian Jira or Azure DevOps.

The attachments of the Version are not taken over when a new Version is created.

To edit the project details, click on the “Edit” button in the toolbar. The project title is a mandatory field.

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 sidebar to get a list of all Test Suites in the currently selected Version. By default, Test Suites 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 edit, pin, copy or delete Test Suites, use the context menu on the right-hand side or right-click on the corresponding Test Suite. To delete a Test Suite, it must be unlocked and not part of any Test Run.

Each Test Suite is separated into three sections:

• Overview: Information about the Test Suite and its content.
• Test Cases: A tree of all folders and Test Cases in the Test Suite.
• Related Test Runs: A list of all Test Runs that the Test Suite is a part of. Even Test Runs of other Versions of the Project are listed here.

When a Test Suite is selected, Q12-TMT navigates to the “Test Cases” section.

Overview

The overview of a Test Suite displays the name, ID, description, and priority. The default priority is “Medium” . Add tags and attachments in the corresponding sections. The “Internal” section includes, for example, time booking information for the Test Suite. The “Metadata” section contains storage and execution data.

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.

The Test Cases tree groups all the Test Cases in a specific Test Suite. Use folder to organise Test Cases into a hierarchical structure representing different scenarios.

The following functions are available in the tree structure.
Toolbar:

• + Test Case: Add a new Test Case.
• + Folder: Add a new folder.
• arrange: Adjust the order of the Test Cases and folders.
• bulk operation: Move, copy, or edit specific parameters all at once.
• expand/collapse: Collapse or expand all folders.

New objects added via the toolbar appear at the end of the list and are sorted manually.

For each Test Case, at the end of a row (incl. context menu):

• edit Test Case: Open the Test Cases in edit mode.
• open in new tab: Open the Test Case in a new tab.
• pin Test Case: Pin the Test Case for later use through the pin board.
• print: Create a PDF of the Test Case.
• copy: Copy a Test Case into any Test Suite.
• move: Move a Test Case within the current Test Suite.
• delete: Delete the Test Case from the currently selected Version.

For each folder, at the end of a row (incl. context menu):

• edit folder: Open the folder in edit mode.
• open in new Tab: Open the folder in a new tab.
• + Test Case: Add a new Test Case to this folder.
• + Folder: Add a new folder to this folder.
• copy: Copy a folder into any Test Suite.
• move: Move a folder within the current Test Suite.
• delete: Delete the folder from the currently selected Version.

Open the context menu by clicking the three dots at the end of the line, or by right-clicking the Test Case or folder row. Some functions are temporarily locked when another user is editing. Test Cases and folders can be deleted when they are not part of an open Test Run and not locked.

Create & Edit

The title and status are mandatory fields in a Test Case.

The following Test Case sections are editable:

• Test information: Basic information such as status and prioritization for a Test Case. Assign users who have access rights to the Project.
• 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: Risk values for all risk categories for the selected Test Case.
• Attachments: Files can be uploaded here (e.g. a diagram or target state screenshot).
• 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.

Copy & Move

Copy:
Test Cases and folders can be copied:

• at any time
• within the currently selected Test Suite
• within the currently selected (Sub)Project version
• into a Test Suite of another Version of the same (Sub)Project
• into a Test Suite of another Subproject within the same Project

Copying is available within the same Project and its Subprojects. The copy form displays all assigned Subprojects.

Move:
Move Test Cases and folders that are unlocked and not part of an open Test Run. Moving works within the currently selected Version.

Details

Click a Test Case to open the details. If the Test Case is located in a folder or subfolder, the path is displayed above the toolbar. All fields available during creation are displayed, along with the “Metadata” section appears. The buttons for pinning, expanding, collapsing, and closing the Test Case details are located in the upper right-hand corner.

The toolbar contains the following buttons:

• edit: Open the Test Cases in edit mode.
• print: Create a PDF of the Test Case.
• copy: Copy a Test Case into any Test Suite.
• move: Move a Test Case within the current Test Suite.
• delete: Delete the Test Case from the currently selected Version.
• history: Change to the Test Case in chronological order.
• related Test Runs: Test Runs of all Versions related to the Test Case.

Print a Test Case to a single PDF from the details view. The PRF contains the Test Case data, including the data and time of creation. Metadata, attachments, and general information (e.g. status, type, or automation) are not included.

Clicking the “Test Run” to button open a list of all Test Runs from the currently selected Version and all other Versions where the Test Case was executed. Each entry shows the assigned testers, the test result, and any stored tickets. Use the context menu to navigate to the Test Case in the Test Run or to the entire Test Run.

Version Delta

The version delta identifies Test Cases added or changed in the currently selected Version. Filter Test Cases by their version delta in Search or in a Test Run via Smart-Selection. This focuses the Test Run selection on new or changed features compared to the previous Version.

Q12-TMT sets the Version Delta to “yes” by default when a user adds or edits a Test Case. Set it to “yes” and “no” manually at any time.

Risk

This section displays all risk levels and risk parameters per risk level for a single Test Case.

The section is divided into four sub-areas:

• overall
• business logic
• test history
• release scope

Overall
Calculated value for all existing risk levels, resulting in an automatic overall evaluation of the risk for a Test Case.

Business Logic
Assign values manually in this section. The slider defaults to “Auto” for automatic calculation. Set it to “Manual” to select the occurrence of an error and its impact. Both values are required for the Business Logic risk calculation.

These parameters help to assess the likelihood of an error occurring in production and its potential impact.

Test History
The non-editable area shows the risk of a Test Case based on its test history. For more information, see the chapter on Risk Based Testing.

Release Scope
The non-editable area shows the risk depending on the release scope. For more information, see the chapter on Risk Based Testing.

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. When executing the Test Case in a Test Run, each test step result can be documented.

At the end of a test step (incl. context menu):

• ▲/▼(Up/Down): Change the order of the test steps.
• add above: Insert a new test step above.
• add below: Insert a new test step below.
• copy: Copy the test step.
• delete: Delete the test step.

Below the test steps:

• add: Insert a new test step at the end

Use drag and drop to change the position of test steps.

History

Click the history icon in the toolbar to open the Test Case history. The history lists all changes in chronological order, starting with the creation.

Each entry includes the corresponding metadata, e.g. the user who created or edited the Test Case, the exact date, time, and version number.

Each edit saves the original and new content for every changed field. Colours highlight the changes: green for additions, red for deletions.

Tags

Tags are used to categorise different Test Cases of Test Suites. The input value is a string, separated by a space, comma or semicolon.

In the “Risk-based testing” section tags are used to classify Test Cases for possible regression testing.

Filter by tags in the search results or Smart-Select function to get an overview of, for example, Test Cases across all Test Suites of the (Sub)Project.

There are several limits for tags:

• no whitespaces
• minimum number of characters: 1
• maximum number of characters: 30
• not case-sensitive
• no limit on tags per Test Case

Tags apply to the whole Project and all Subprojects, and can be assigned to multiple Test Cases. After entering the first character, a dropdown opens with matching options sorted alphabetically. The list updates while typing.

Related Test Runs

The “Related Test Runs” section lists all Test Runs the Test Suite is part of. The overview displays the title, ID, created on / closed on, state and version number Click a Test Run to open it.

Test Runs

A Test Run is a collection of Test Cases to execute in the current Version. Select multiple Test Suites and choose the specific Test Cases to execute together in a Test Run.

Create a new Test Run for each execution. To re-execute the same set of Test Cases, copy the Test Run.

Click on the icon in the sidebar to open a list of all Test Runs of the currently selected Version.

The overview shows the Test Runs states, the percentage of executed Test Cases, and detailed test results information.

The following functions are available in the overview.
Toolbar:

• + Test Run: Create a new Test Run.
• bulk operation: Edit tester assignment all at once.
• filter: Access the filter mask to filter the Test Runs.

For each Test Run, at the end of a row (incl. context menu):

• edit: Open the Test Run overview in edit mode.
• open in new tab: Open the Test Run in a new tab.
• pin Test Run: Pin the Test Run for later use through the pin board.
• generate report: Create a PDF file with information about the Test Run.
• copy: Copy the Test Run without any result or result detail.
• delete: Delete the Test Run from the Version.

Open the context menu by clicking the three dots at the end of the line, or by right-clicking the Test Run row. Delete a Test Run when it contains no Test Suites.

The sidebar of the open Test Run contains the “Create report” button, the copy icon, and the following sections:

• Overview: Information about the Test Run and the content.
• Test selection: Test Suites and Test Cases are added to or removed from the Test Run in this area.
• Test scope: Overview of all Test Cases assigned to the Test Run.
• Result map: Results diagram for visualizing the execution status of all Test Cases in a Test Run and their hierarchical structure.
• Risk-Burndown: A visual visualization of test progress with total & remaining overall risk

Create & Edit

To create a new Test Run, click the “+ Test Run” button above the Test Run list. To edit a Test Run, click the “Edit” button at the end of the Test Run row or in the Test Run overview. The title is mandatory. A new Test Run defaults to the state “Open”.

Setting the status to “In Progress” freezes the risk values of the Test Cases. These values feed into the risk-based testing charts. An open Test Run can be edited at any time.

tip

Tip
A Test Run can also be created directly by clicking the “Create Test Run” button in the Test Case search results or in the Test Suite view. The title and description are filled in automatically.

Assign Testers

Assign testers to a single Test Case, multiple Test Cases, Test Suites, or whole Test Runs. Q12-TMT automatically sends an email to the assigned user. Assign users who have access rights in the current Project.

Use bulk operations to assign testers to one or more objects in all sections. A message in the upper right-hand corner provides information about the status of the background process.

When a tester is assigned to a Test Run, all Test Cases contained therein are automatically assigned to them. If some Test Cases are already assigned to other people, a message appears with the options to keep the existing tester or replace them. To quickly add testers to Test Cases from different Test Suites within a Test Run, use the feature in the “Test scope” section.

It is possible to select or change a tester during the test.

Smart-Select

The “Smart-Select” feature allows users to automatically select or deselect Test Cases that fit certain characteristics.

In the “Test Suite selection” section, run this function for Test Cases in all Test Suites of the currently selected Version, or for Test Suites already added to the Test Run. Choose whether the Test Case matches all specified values or one of them.

Click the “Select matches” button to add corresponding Test Cases to the Test Run. Click the “Deselect matches” button to remove all corresponding Test Cases from the Test Run.

A message in the upper right corner provides information about the status of the background process.

Click on the “Undo” button to undo the changes. This option is available until the next manual change is made or until the page is left.

Test Case in Run

Test Cases in a Test Run are read-only copies of the Test Cases in the Test Suites menu. The detailed views differ in a few things.

Q12-TMT copies the Test Case name, ID, tags, and the Description, Precondition, and Test Steps sections from the original Test Case. In the Test Run view, the “Result” column supplemented the table of test steps.

The ID in the run, the tester, and the “Attachments” and “Overall test result” sections are specific to the Test Run. The path of the Test Case in Run is displayed above the toolbar.

The following functions are available in the view.
Toolbar:

• execute test: Open the Test Case in Run in execution mode.
• print: Create a PDF file with information about the Test Case in Run.
• history: Change to the Test Case in Run in chronological order.
• show original: Open the original Test Case on the right.

In the “Show original” view, adjustments can be made using the “Edit” button. The derived Test Case in the Test Run is updated automatically.

Bug Intelligence Assistant

info

This feature requires a specific license plan.
The IT administration controls access to this AI feature for each (Sub)Project.

The Bug Intelligence Assistant summarises previous defect tickets and highlights potentially critical areas of a Test Case. Click the button in the Test Case in Run view. After a short loading period, Q12-TMT displays a list of defects and a summary of their contents.

Summary
The summary provides a short impression of the previously found defects and the most important information. If the AI function is disabled, a notification message will appear instead of the summary.

Defect list
The defect list displays all tickets linked in the “Defects” field of Test Cases in Run that are associated with the original Test Case across all Versions. The ticket number, priority, title, and the Version in which the ticket was linked are shown. If a ticket is linked in different Versions, the latest Version is displayed in the table.

Overview

After selecting a Test Run, the “Overview” section opens. All stored information, as well as the related attachments and metadata, are displayed.

The “Test results” section appears after at least one Test Case has been assigned. A pie chart reflects the results of all included Test Cases. A further, more detailed graph is available in the “Result map” section.

The “In Progress” status freezes the current risk values of the associated Test Cases for use in the risk burndown chart, while the “Closed” status indicates that the test is complete.

Each status change triggers a background process. The process runs when no Test Case is locked. If Test Cases are locked, Q12-TMT displays a message with two options: cancel the process, or start it in wait mode. In wait mode, the process starts automatically once all Test Cases are unlocked.

The following functions are available in the view.
Toolbar:

• edit: Open the Test Run overview in edit mode.

info

Changing the status requires the test manager or project administrator role

Test Selection

The “Test Selection” section lists all Test Suites selected for the Test Run, including the number of Test Cases selected and the priority of each Test Suite.

A new Test Run has an empty list.

The following functions are available in the view.
Toolbar:

• + Test Suite: Add multiple Test Suites from the currently selected Version.
• smart-Select: Automatic selection and deselection of Test Cases based on certain criteria.
• arrange: Adjust the order of the Test Suites.
• bulk operation: Edit tester assignment all at once.

For each selected Test Suite, at the end of a row (incl. context menu):

• manage: Open the Test Case selection in edit mode.
• open in new tab: Open the Test Suite in a new tab.
• show details: Show the “Overview” section of the Test Suite.
• edit for Test Run: Allow to make changes to the Test Suite details that only apply to the Test Run.
• remove from Test Run: Remove the Test Suite, including all related Test Cases, from the Test Run.

To open the context menu, click the three dots at the end of the line, or right-click the Test Suite row.

Test Suite Selection

Click on the “+ Test Suite” button in the toolbar in the “Test selection” section, to display a list of all available (and currently not selected) Test Suites of the (Sub)Project.

Select the Test Suites containing the Test Cases to execute. After adding a Test Suite, select the Test Cases to include in the Test Run.

The following functions are available in the view.
Toolbar:

• search: Filter the list for a searched term.
• filter: Access the filter mask to filter the Test Suite list

Test Suite in Run

In the “Test Selection” tab, click “Show details” in the last table column to open the Test Suite details. Test Suites in a Test Run are read-only copies from the Test Suites menu. Q12-TMT copies the title, ID, priority, description, attachment, and internal sections from the original Test Suite.

The following functions are available in the view.
Toolbar:

• edit: Change the Test Suite priority for the Test Run.
• remove: Removes the Test Suite, including all related Test Cases, from the Test Run.

Test Case Selection

Select the Test Suite to see the Test Cases that are already added to the Test Run. This overview shows the Test Case title, ID in Run, ID, assigned tester and assignee, tags, the test result and linked defects.

The following functions are available in the view.
Toolbar:

• manage: Open the test selection in edit mode. The “Smart-Select” function is available.
• bulk operation: Edit tester assignment and overall test result all at once.
• expand/collapse: Collapse or expand all folders.

For each selected Test Case, at the end of a row (incl. context menu):

• execute Test: Open the Test Case in Run in execution mode.
• open in new tab: Open the Test Case in a new tab.
• pin Test Case in Run: Pin the Test Case in Run for later use through the pin board.
• print: Create a PDF file with information about the Test Case in Run.

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. A Test Case can be selected to view its details .

Test Scope

In the “Test scope” section, all added Test Cases of the Test Run are displayed in a flat list. This provides a quick overview of the Test Cases with and without assigned testers, test results, risk assessment and any defects (tickets).

The following functions are available in the view.
Toolbar:

• bulk operation: Edit tester assignment and overall test result all at once.
• filter: Access the filter mask to filter the Test Suite list.

For each selected Test Case, at the end of a row (incl. context menu):

• execute Test: Open the Test Case in Run in execution mode.
• open in new tab: Open the Test Case in a new tab.
• pin Test Case in Run: Pin the Test Case in Run for later use through the pin board.
• print: Create a PDF file with information about the Test Case in Run.

Q12-TMT temporarily locks some functions during editing.

Test Execution

Once test execution starts, the Test Case enters edit mode and Q12-TMT locks it for other users. If a defect or result details are added, the overall result cannot be set to “Untested”. Select a result for each individual test step as needed. The overall result can be set independently of test step results.

Click the button next to each step to mark it as passed. Click the button to enter a custom result. A custom result displays an information icon next to the test step result. Hover over the icon to view the content. This helps locate errors and supports them with useful information, e.g. the error message.

Two additional input fields are available to document defects and result details during execution.

Add screenshots, log files, and other attachments to the Test Case in the “Attachments” section. For more information, see chapter “Attachments”.

Close editing mode by clicking “Cancel”, “Save”, or “Save and Next”. “Save and Next” saves the changes and opens the next Test Case for editing, unless it is the last entry.

Test Execution History

The history for Test Cases in Runs lists all edits of the test execution and the original Test Case. This shows whether the last execution reflects the latest state of the Test Case. The history stops recording changes after the Test Run is closed.

Result map

The result diagram shows all Test Suites, folders, subfolders and Test Cases included in the Test Run, and the overall progress of the execution.

The test results are divided into four different execution statuses.

Execution status	Test result
Untested	Untested
Passed	Passed
In Execution	In Progress, On Hold (internal), On Hold (external), Retest, Blocked, Customer, Skipped
Failed	Failed (known), Failed (new)

A pie chart showing the overall progress and the four execution statuses is displayed in the center. The selected Test Suites initially start from this central point. This is followed by folders with any subfolders, if available, and finally the selected Test Cases.

When the mouse pointer is moved over a point, information about the type (Test Suite, folder, or Test Case in the run) appears with the name and ID. An animation appears to illustrate the direct connection between the connected points. Points can be moved to another position using drag and drop. The mouse wheel can be used to zoom in or out of the diagram.

Risk Burndown

In the risk burndown chart, the total and remaining overall risk is displayed on the y-axis against the (executed and remaining) Test Cases on the x-axis.

The x-axis is divided into two parts.

• A left part displaying the executed Test Cases and
• A right part displaying the remaining Test Cases (= not yet executed).

The various test results are divided into two statuses.

Status	Test result
Executed Test Cases	Passed, Failed (new), Failed (known)
Remaining Test Cases	Untested, In Progress, On Hold (internal), On Hold (external), Retest, Blocked, Customer, Skipped

To display the cumulative total risk value, the risk values are frozen as soon as the Test Run has the status “In progress”. After this point, any changes of the risk values of the Test Cases in the run will no longer be taken into account for this Test Run. Test Cases with an undefined risk are included with a risk value of 0.

Create Report

Information about “Create Report” from 1:00

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.

A notification appears while the report generates. Download the report when it is ready.

info

Reports are available in German and English language. The language can be set with further access rights in the system configuration. For more information please see the Administration Guide to do so.

My Tasks

If a user is assigned to a Test Case, Q12-TMT automatically sends an email. Assign a user as “Assignee” in a Test Case in the Test Suite, or as “Tester” in the Test Case in a Test Run. The “My Tasks” icon in the sidebar shows the number of assigned objects. Test Cases with an open status appear in this section.

Click the My Tasks icon in the sidebar to open an overview grouped by task type. Each category shows the number of assigned Test Cases below the button. A category without assigned Test Cases is inactive.

After selecting a category, a list of all Test Cases of that type assigned to the user appears. Click on a line to open the object in view mode.
The following functions are available in this overview.
For each Test Case in “Assignee of Test Cases”, at the end of a row (incl. context menu):

• edit Test Case: Open the Test Case in edit mode.
• open in new tab: Open the Test Case in a new tab.
• pin Test Case: Pin the Test Case for later use through the pin board.

For each Test Case in “Tester of Test Cases”, at the end of a row (incl. context menu):

• execute test: Open the Test Case selection in execution mode.
• open in new tab: Open the Test Case in Run in a new tab.
• pin Test Case in Run: Pin the Test Case in Run for later use through the pin board.
• print: Create a PDF file with information about the Test Case in Run.

Risk-Based Testing

info

This feature requires a specific license plan.

Q12-TMT offers a structured approach to optimizing testing efforts with its risk-based testing function. Risk values are determined on the basis of manual input and automated algorithms, which are used to select and prioritize specific Test Cases.

Clicking on the risk icon in the sidebar opens the “Risk-based testing” menu and the risk heatmap.

The display is divided into four risk categories

• Heatmap
• Business logic
• Test history
• Release scope

General

Full risk calculation for “Test History” and “Release Scope” requires a connected ticket system such as Jira or Azure DevOps.

The different risk levels are displayed in a pie chart for the views “Business Logic”, “Test History” and “Release Scope”. The size of the segments is proportional to the number of Test Cases in the respective level.

Hover over a segment to see additional details in a tooltip. Click “Show Test Cases” to open a list of Test Cases for the corresponding risk level, or click “Create Run” to create a Test Run with those Test Cases.

The legend on the top right lists the percentage and number of Test Cases in each risk level. The “Executed & included in Test Run(s)” section shows the number of Test Cases executed among those which are part of a Run. Test Cases are grouped by risk level. Clicking on a line in the legend opens a list of Test Cases for the corresponding risk level.

The following functions are available in this view.
Toolbar:

• create run: Create a Test Run with all listed Test Cases. The title of the Test Run is filled automatically and contains the corresponding risk level.

Context menu:

• edit: Open the Test Case in edit mode alongside the current table.
• open in new tab: Open the Test Case in a new tab.
• pin Test Case: Pin the Test Case for later use through the pin board.

Open the context menu by clicking the three dots at the end of the line, or by right-clicking the corresponding row.

Heatmap

The heatmap is a combination of all other levels. The risk displayed in the heatmap corresponds to the average of the risk assessments of the Test Case on all other levels.

The diagram shows the risk scores of the Test Cases for each Test Suite. When moving the mouse over or highlighting via the keyboard, the corresponding Test Suite, the number of Test Cases per risk level, and the total number of Test Cases involved are displayed.

Business Logic

Q12-TMT assesses the risk by considering the likelihood and impact of an error occurring in the current Test Case.

Three parts are available for each segment of the pie chart:

• outermost part: Number of Test Cases outside of any Test Run in the currently selected Version.
• middle part: Amount of Test Cases included in any Test Run (open, in progress or closed) in the currently selected Version and are not executed
• innermost part: Amount of Test Cases included in any Test Run (open, in progress or closed) in the currently selected Version and are executed (i.e., with status “Passed”, “Failed (new)” or “Failed (known)”

Hover over the pie chart fields to see all combinations of likelihood and impact for the corresponding risk level, and the number of Test Cases per combination (bottom right). The top right value shows the Business Logic risk score used to calculate the overall risk.

Required input

• Test Case: “Risk” section, value for “Likelihood”
• Test Case: “Risk” section, value for “Impact”

For automatically calculated values of “Likelihood” and “Impact”:

• Stored keywords in the project settings (only for the project administrator)
• Add keywords to the Test Case title or (sub)folder title
• Test Case: Value for “Prioritization”

Test History

Q12-TMT assesses the risk of a Test Case based on its execution history. This includes the frequency and severity of failed executions across all Versions.

Q12-TMT estimates the average severity of failures by analyzing the priority of linked defect tickets across all previous executions. The error frequency is determined by comparing failed executions (“Failed (new)” and “Failed (known)”) to the total executions across all Versions, including the currently selected Version.

Three parts are available for each segment of the pie chart:

• outermost part: Number of Test Cases outside of any Test Run in the currently selected Version.
• middle part: Amount of Test Cases included in any Test Run (open, in progress or closed) in the currently selected Version and are not executed.
• innermost part: Amount of Test Cases included in any Test Run (open, in progress or closed) in the currently selected Version and are executed (i.e. with status “Passed”, “Failed (new)” or “Failed (known)”.

Hover over the pie chart fields to see all combinations of frequency and severity that match corresponding risk level, and the number of Test Cases per combination (bottom right). The top right value shows the risk score.

Required input

• Execution of a Test Case in a Test Run (across Versions)

If a ticket system is integrated:

• Test Run: “Overall test result” section, field “Defects”
• ticket field “Priority”

Release Scope

The release scope assesses risks by analyzing the software release that is under test. This is achieved by assessing linked source or defect tickets.

For source tickets, Q12-TMT compares the release version in the currently selected Version project details with the fix version of linked tickets. If the versions match, the Test Case is a feature test. Q12-TMT assigns feature tests a high or medium risk, depending on the priority of the source ticket.

If the Test Case has defects that are linked in an open or closed Test Run, Q12-TMT treats it as a defect retest with risk level from high to low.

If a tag exists in a Test Case and also exists in a feature test or defect retest, the Test Case automatically becomes part of a regression test.

Q12-TMT assigns all other Test Cases either an undefined risk (if version delta is enabled) or a low risk (if version delta is disabled).

Required input

If a ticket system is integrated:

• in Test Case: “Sources” section, field “Tickets”
• in Test Run: “Overall test result” section, field “Defects”
• in Test Case: “Criteria” section, field “Tags”
• ticket field “Priority”
• ticket field “Fix Version”

Test automation

Click the test automation icon in the sidebar to open the “Test Automation” menu.

Pie chart
The different automation statuses are displayed in a pie chart. The size of the segments is proportional to the number of Test Cases in the respective automation status. Additional details are displayed in a tooltip when the mouse is moved over the segments. Two buttons appear in the tooltip. Click on the “Show Test Cases” button to open a list of Test Cases for the corresponding automation status. Click “Create Run” to create a Test Run with the Test Cases for the corresponding automation status.

Legend
The legend on the top right lists the percentage and number of Test Cases in each automation status. Click a line in the legend to open a list of Test Cases for the corresponding automation status.

Test Case table
The following functions are available in this view.
Toolbar:

• create run: Create a Test Run with all listed Test Cases. The title of the Test Run is filled automatically and contains the corresponding automation status.

Filter bar:

• Status: Narrow the listing to the selected Test Case statuses.
• Assignee: Narrow the listing to the selected assignee.

Versions

Q12-TMT supports semantic and parallel versioning, allowing conflict-free testing across multiple Versions. It tracks Test Case history, providing full visibility into past results and progress.

Create a Q12-TMT Version for each software release. Q12-TMT copies all Test Suites (including the Test Case Tree) from the source Version and retains the assignee. Test Runs are not included.

All existing Versions (open and closed) are displayed in an overview for the (Sub)Project. This overview is available in the project structure (My Projects) and in the open (Sub)Project.

Project structure	After selecting a (Sub)Project
To open the Version overview, right-click a (Sub)Project in My Projects and select the version icon from the context menu. Users with the required permissions can create or delete Versions in this overview. Delete Versions only while they are open.	Click the Version icon in the sidebar to open the Version overview. Select another Version from this overview.

info

Creating a new Version requires the project administrator role.

Create a new Version

To create a new Version, click the plus button next to the source Version. Select a version number from the dropdown and enter a title. Add key points, a description, release versions and attachments as needed.

Q12-TMT uses the stored release version to determine the “Release Scope” risk values. The release version corresponds to the software release under test and the “Fix Version” maintained in the ticket system, e.g. Atlassian Jira or Azure DevOps.

Close a Version

Close a Version in the “Version” section in the project details. This requires additional access rights. A notification appears at the top of the screen for all users in the currently selected Version. A message in the top right area indicates when the background process starts and ends.

Closed Versions are in read-only mode and all data (including risk value) is frozen. Use closed Versions as basis for new Versions. Test Cases and (sub)folders can still bw copied into open Versions.

Keyword changes for risk-based testing in the (Sub)Project settings apply to open Versions only. Closed Versions retain their existing values and categorisation.

Privacy & Legal Terms

The Privacy Policy and Terms & Conditions of Q12-TMT can be found in the “About” section of Q12-TMT.

Click on the “About” button to open a dropdown menu. 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.