# Get started with TMS integration

> **TL;DR**
> TMS tool window: `View | Tool Windows | TMS`
>
>
>
> TMS settings: `Settings | Tools | TMS`

> **Note:**
> In order to use test management tools covered in this section, make sure that the [Test Management](https://plugins.jetbrains.com/plugin/15109-test-management) plugin is [installed and enabled](managing-plugins.html).

The Test Management plugin  provides integration with test management tools for more transparent interaction between the DEV and QA teams. It supports browsing test suites and case hierarchies, navigation for TMS items, generates unit tests for selected test scenarios, and helps find non-automated test cases or obsolete test methods.

## Connect to a remote TMS

While you cannot change test data in a remote TMS, you can still benefit from the integration by linking test data and code. For example, this is useful when searching for [outdated tests](#find-outdated) or [candidates for automation](#find-candidates-for-automation).

Procedure:

1. Press `Ctrl+Alt+S` (Windows), `⌘ Comma` (macOS), `⌘ Comma` (IntelliJ IDEA Classic (macOS)), `⌘ Comma` (macOS System Shortcuts), `Ctrl+Alt+S` (XWin), `Ctrl+Alt+S` (GNOME), `Ctrl+Alt+S` (KDE), `Ctrl+Alt+S` (Emacs), `Ctrl+Alt+S` (Sublime Text), `⌘ Comma` (Sublime Text (macOS)), `Ctrl+Alt+S` (NetBeans), `Ctrl+Alt+S` (Visual Studio), `⌘ Comma` (Visual Studio (macOS)), `Ctrl+Alt+S` (Eclipse), `⌘ Comma` (Eclipse (macOS)) to open settings and then select `Tools | TMS`.

2. In Remote Connections, click Add and select TestRail.

> **Note:**
> Currently, only TestRail 6.7 or later is supported.

Other test management systems will be added in future releases. Feel free to vote for the corresponding requests:

* [IDEA-268401 - TestLink](https://youtrack.jetbrains.com/issue/IDEA-268401)

* [IDEA-268399 - Xray for Jira](https://youtrack.jetbrains.com/issue/IDEA-268399)

* [IDEA-268393 - Zephyr](https://youtrack.jetbrains.com/issue/IDEA-268393)

3. Specify:

* URL, including the protocol prefix, for example, `https://mytms.testrail.net`

* login and password for the remote TMS

4. Optionally, [configure a proxy](settings-http-proxy.html).

5. After you have entered valid credentials, specify the test project within the TMS.

## Browse and navigate

After you have configured the connection to a test management system, the data gets synchronized and the list of TMS items appears in the TMS tool window. TMS item is the umbrella term for objects that represent test suites, test cases, and test runs in a test management system.

When you browse them, the preview window shows additional details about the selected element.

![TMS tool window](https://resources.jetbrains.com.cn/help/img/idea/2026.2/aqua_tms_tool_window.png)

You can filter the list of TMS items in the TMS tool window according to specific criteria like tags, metadata, and so on.

Procedure: Filter items

1. On the toolbar of the TMS tool window, click Edit Filters.

![Filter items in TMS tool window](https://resources.jetbrains.com.cn/help/img/idea/2026.2/aqua_edit_filters.png)

2. In the Edit Filters dialog, specify the criteria, according to which you want to filter the available TMS items.

After you click OK, the TMS tool window gets updated, and all irrelevant items are filtered out.

Search Everywhere allows you to quickly search for TMS items.

Procedure: Search for TMS items

* Go to `Navigate | TMS Item`.

Alternatively, press `Shift` (Windows), `Shift` (macOS), `Shift` (IntelliJ IDEA Classic (macOS)), `Shift` (macOS System Shortcuts), `Shift` (XWin), `Shift` (GNOME), `Shift` (KDE), `Shift` (Emacs), `Shift` (Sublime Text), `Shift` (Sublime Text (macOS)), `Shift` (NetBeans), `Shift` (Visual Studio), `Shift` (Visual Studio (macOS)), `Shift` (Eclipse), `Shift` (Eclipse (macOS)) twice and specify the `/tms` prefix followed by your query.

When a TMS item ID is mentioned in a source code comment, you can open a quick preview for it.

Procedure: Preview a TMS item from a comment

* Hold `Ctrl` (Windows), `Ctrl` (macOS), `Ctrl` (IntelliJ IDEA Classic (macOS)), `Ctrl` (macOS System Shortcuts), `Ctrl` (XWin), `Ctrl` (GNOME), `Ctrl` (KDE), `Ctrl` (Emacs), `Ctrl` (Sublime Text), `Ctrl` (Sublime Text (macOS)), `Ctrl` (NetBeans), `Ctrl` (Visual Studio), `Ctrl` (Visual Studio (macOS)), `Ctrl` (Eclipse), `Ctrl` (Eclipse (macOS)) and click the TMS item ID in the comment.

![Preview TMS items from comments](https://resources.jetbrains.com.cn/help/img/idea/2026.2/aqua_tms_preview.png)

From the TMS tool window, you can get the list of all places that refer to the selected TMS item.

Procedure: Locate referring code

* In the TMS tool window, right-click a TMS item and select Find Usages. Alternatively, select a TMS item and press `Alt+F7` (Windows), `⌥ F7` (macOS), `⌥ F7` (IntelliJ IDEA Classic (macOS)), `⌃ U` (macOS System Shortcuts), `Alt+F7` (XWin), `Alt+Shift+7` (GNOME), `Alt+Shift+7` (KDE), `Alt+F7` (Emacs), `Alt+F7` (Sublime Text), `⌥ F7` (Sublime Text (macOS)), `Alt+F7` (NetBeans), `Shift+F12` (Visual Studio), `⇧ F12` (Visual Studio (macOS)), `Ctrl+G` (Eclipse), `⌘ ⇧ G` (Eclipse (macOS)).

![Locate referring code](https://resources.jetbrains.com.cn/help/img/idea/2026.2/aqua_tms_find_usages.png)

> **Note:**
> This feature works more precisely for tests marked with [TMS link annotations](tms-annotations-setup.html).

## Analyze

You can find test cases that are still not covered by unit tests and could possibly be automated. This is possible because of TMS link annotations, which serve as the guide for the analysis.

> **Note:**
> The features described in this chapter only work for tests marked with [TMS link annotations](tms-annotations-setup.html).

Procedure: Find candidates for automation

1. On the toolbar of the TMS tool window, click Edit Filters.

![Find candidates for automation](https://resources.jetbrains.com.cn/help/img/idea/2026.2/aqua_edit_filters.png)

2. In the Edit Filters dialog, specify Only non-referenced from code.

![Edit Filters dialog](https://resources.jetbrains.com.cn/help/img/idea/2026.2/aqua_tms_edit_filters_dialog.png)

Sometimes it happens that a test case has been removed from the TMS and is no longer relevant, however there are still some unit tests that cover it. Not only such tests clutter the codebase, they also take time to execute. TMS plugin helps you find such outdated tests.

Procedure: Find outdated tests

* On the toolbar of the TMS tool window, click Find Unresolved TMS Links.

![Find outdated tests](https://resources.jetbrains.com.cn/help/img/idea/2026.2/aqua_tms_unresolved_links.png)

The results are shown in the Problems tool window.

## Generate unit tests

You can generate unit tests for a test case right from the TMS tool window. Unit test generation is only available for Java, Kotlin, and Python.

Procedure:

1. Select one or more test cases in the TMS tool window and click New Test from Test Cases on the toolbar.

![Generate unit tests](https://resources.jetbrains.com.cn/help/img/idea/2026.2/aqua_generate_test.png)

2. Enter the name for the test class and select the module/package where it will be located.

A test class is generated and populated with test cases, which in turn contain test steps as commented code. The generated piece is framework-agnostic, so you can use it with any testing framework with little customization.

![Test class is generated and populated with test cases](https://resources.jetbrains.com.cn/help/img/idea/2026.2/aqua_tms_generate_test_result.png)

> **Tip:**
> Alternatively, you can copy a test case from the TMS tool window and paste it in the editor. If a suitable context is found, the test case will be converted to unit test boilerplate.
>
>
>
> To copy a test case, select the desired one and press `Ctrl+C` (Windows), `Ctrl+C` (macOS), `Ctrl+C` (IntelliJ IDEA Classic (macOS)), `Ctrl+C` (macOS System Shortcuts), `Ctrl+C` (XWin), `Ctrl+C` (GNOME), `Ctrl+C` (KDE), `Ctrl+C` (Emacs), `Ctrl+C` (Sublime Text), `Ctrl+C` (Sublime Text (macOS)), `Ctrl+C` (NetBeans), `Ctrl+C` (Visual Studio), `Ctrl+C` (Visual Studio (macOS)), `Ctrl+C` (Eclipse), `Ctrl+C` (Eclipse (macOS)). You can also click the Copy button located in the test case preview, or right-click the test case and select the Copy option from the menu.
>
>
>
> ![Copy test case](https://resources.jetbrains.com.cn/help/img/idea/2026.2/aqua_copy_test_case.png)

If you are working with a specific testing framework, you might want to customize the template so that the generated code conforms to the conventions and has required annotations in place.

Procedure: Customize the template

1. Press `Ctrl+Alt+S` (Windows), `⌘ Comma` (macOS), `⌘ Comma` (IntelliJ IDEA Classic (macOS)), `⌘ Comma` (macOS System Shortcuts), `Ctrl+Alt+S` (XWin), `Ctrl+Alt+S` (GNOME), `Ctrl+Alt+S` (KDE), `Ctrl+Alt+S` (Emacs), `Ctrl+Alt+S` (Sublime Text), `⌘ Comma` (Sublime Text (macOS)), `Ctrl+Alt+S` (NetBeans), `Ctrl+Alt+S` (Visual Studio), `⌘ Comma` (Visual Studio (macOS)), `Ctrl+Alt+S` (Eclipse), `⌘ Comma` (Eclipse (macOS)) to open settings and then select `Editor | File and Code Templates`.

2. Open the Other tab, select the required template under Unit test templates for TMS, and modify it as needed.

For more information about templates and their syntax, refer to

[File templates](using-file-and-code-templates.html) and

[official documentation for Apache Velocity Template Language](https://velocity.apache.org/engine/1.7/user-guide.html).

## See also