# Explore test results

> **TL;DR**
> Open the Run tool window: `View | Tool Windows | Run` ( `Alt+4` (Windows), `⌘ 4` (macOS), `⌘ 4` (IntelliJ IDEA Classic (macOS)), `⌘ 4` (macOS System Shortcuts), `Alt+4` (XWin), `Alt+4` (GNOME), `Alt+4` (KDE), `Alt+4` (Emacs), `Alt+4` (Sublime Text), `⌘ 4` (Sublime Text (macOS)), `⌘ 6` (Xcode), `Alt+4` (Visual Studio), `⌘ 4` (Visual Studio (macOS)), `Alt+4` (ReSharper), `⌘ 4` (ReSharper (macOS)), `Alt+3` (QtCreator), `⌘ 3` (QtCreator (macOS)), `Alt+4` (NetBeans), `Alt+4` (Eclipse), `⌘ 4` (Eclipse (macOS)) )

CLion shows test results in the Test Runner tab of the Run tool window:

![The Test runner window](https://resources.jetbrains.com/help/img/idea/2026.2/cl_catchtest_testrunner.png)

The console on the right shows the output of the current test session. It allows you to see the detailed information on the test execution and why your tests failed or were ignored.

The test results toolbar located above the list of test results allows you to [show and hide](#sort-test-results) successful and ignored tests, [display how much time]() it took to run each test, [export](#export), [import](#import-test-results), and [sort](#sort-test-results) test results.

![The Test Runner toolbar](https://resources.jetbrains.com/help/img/idea/2026.2/cl_test_runner_toolbar.png)

Next to each test on the run configuration tab, the IDE shows the test status icon:

| Icon | Description |
| --- | --- |
|  ![Test error](https://resources.jetbrains.com/help/img/idea/2026.2/app.expui.run.testError.svg)  | Test error. This status is assigned to tests that caused an exception from the tested source code.  |
|  ![Test failed](https://resources.jetbrains.com/help/img/idea/2026.2/app.expui.run.testFailed.svg)   | Test failed. If at least one child test fails, all its parent tests are marked as failed.  |
|  ![Test ignored](https://resources.jetbrains.com/help/img/idea/2026.2/app.expui.run.testIgnored.svg)  | Test ignored.      |
|  ![Test in progress](https://resources.jetbrains.com/help/img/idea/2026.2/app.process.step_1.svg)  | Test in progress. |
|  ![Test passed](https://resources.jetbrains.com/help/img/idea/2026.2/app.expui.run.testPassed.svg)  | Test passed successfully. |
|  ![Terminated](https://resources.jetbrains.com/help/img/idea/2026.2/app.expui.run.testTerminated.svg)  | Test terminated. This status is assigned to tests that were stopped.     If at least one test receives this status, then all unfinished tests and their parent tests are marked as terminated.   |

Procedure: Sort and filter test results

Use the following options on the test results toolbar if you want to focus only on the failed tests or if you want to reorganize test results.

* Disable the ![the Show Passed button](https://resources.jetbrains.com/help/img/idea/2026.2/app.expui.run.showPassed.svg) Show Passed option to hide successful tests.

* Disable the ![the Show Ignored button](https://resources.jetbrains.com/help/img/idea/2026.2/app.expui.run.showIgnored.svg) Show Ignored option to hide ignored tests.

* Click ![the Sorting Options button](https://resources.jetbrains.com/help/img/idea/2026.2/app.expui.runConfigurations.sortByDuration.svg) and select how you want to sort the test results:

* Suites Always on Top: display suites on top.

* Sort Alphabetically: sort test results alphabetically.

* By Declaration Order: sort test results in the order in which the tests are declared in the code.

* Sort By Duration: place test nodes on top of the list.

Procedure: Manage test results

* Click ![the More button](https://resources.jetbrains.com/help/img/idea/2026.2/app-client.expui.general.moreVertical.svg) on the test results toolbar and select Test Runner Settings and enable the following options:

![Test runner options](https://resources.jetbrains.com/help/img/idea/2026.2/cl_testrunner_settings.png)

* [Track Running Test](): monitor execution of the current test.

* [Show Inline Statistics]() : view the execution time for tests.

* Scroll To * Scroll to Stack Trace: if a test produced a lot of output (for example, logging) before failing, this option automatically scrolls the output console to the assertion failure once you select the test in the run configuration tab. * Top: scroll to the top of the console output. * Bottom: scroll to the bottom of the console output.

* Show Inline Statistic : show the time of running for each test. ![Unit test statistics](https://resources.jetbrains.com/help/img/idea/2026.2/cl_testrunnertab_statistics.png)

* Open Source at Exception : if you double-click a failed test method on the run configuration tab with this option on, the editor will scroll to the line on which the exception was thrown (instead of scrolling to the test method declaration).

* Navigate with Single Click : open the code for the selected test automatically in the editor.

* Show Auto-Test Status in the Editor: display the [auto-test status indicator](performing-tests.html) in the editor.

* Select First Failed Test When Finished : automatically select the first failed test in the list upon completing the test session.

* Use Wall Time: show the actual real-world elapsed time that passes from the start of a test to its completion, including any delays and waiting caused by system processes.

Procedure: Jump to test declaration

* Select the necessary test from the list on the Test Runner tab and press `F4` (Windows), `⌘ ↓` (macOS), `F4` (IntelliJ IDEA Classic (macOS)), `F4` (macOS System Shortcuts), `F4` (XWin), `F4` (GNOME), `F4` (KDE), `F4` (Emacs), `F4` (Sublime Text), `F4` (Sublime Text (macOS)), `⌘ ↓` (Xcode), `F4` (Visual Studio), `⌘ ↓` (Visual Studio (macOS)), `F4` (ReSharper), `⌘ ↓` (ReSharper (macOS)), `F4` (QtCreator), `F4` (QtCreator (macOS)), `F4` (NetBeans), `F12` (Eclipse), `F3` (Eclipse (macOS)).

> **Tip:**
> To make navigation even faster, use the [Navigate
> with Single Click](#manage-test-results) option.

Procedure: View results of previous tests

CLion automatically saves results of the last 10 test sessions. To open the list of recent test sessions:

* Click the ![Test History](https://resources.jetbrains.com/help/img/idea/2026.2/app.expui.general.history.svg) icon on the test results toolbar and select the necessary test session from the list.

For each test session, the list displays the [run
configuration](run-debug-configuration.html) name and a timestamp:

![Viewing results of previous tests](https://resources.jetbrains.com/help/img/idea/2026.2/cl_testrunnertab_viewprev.png)

You can also [export](#export) test results to a file if you want to keep them or share with your team.

## Export and import test results

Procedure: Export test results to a file

1. Click ![The More button](https://resources.jetbrains.com/help/img/idea/2026.2/app-client.expui.general.moreVertical.svg) on the test results toolbar, then click ![](https://resources.jetbrains.com/help/img/idea/2026.2/app-client.expui.general.export.svg) Export Test Results .

2. Select the format in which you want to save the file:

* HTML : generate an HTML file from a pre-defined template.

* XML : use this format if you want to import this file later to CLion.

* Custom, apply XSL template : use your custom [XSL](https://www.w3schools.com/xml/xsl_intro.asp) template to generate an HTML file from the raw XML output. Click ![Browse button](https://resources.jetbrains.com/help/img/idea/2026.2/app.expui.inline.browse.svg) next to this option and select the `*.xsl` code style definition file.

3. Specify the name of the output file and its location.

4. If you want to open the file in your browser after you export it, select the Open exported file in browser checkbox. Click OK.

Procedure: Import test results

1. To load a previously exported file, click ![Import Tests from File](https://resources.jetbrains.com/help/img/idea/2026.2/app-client.expui.general.import.svg) on the test results toolbar.

If you have not run any tests yet, and the tool window with the test results toolbar is not available, press `Ctrl+Shift+A` (Windows), `⌘ ⇧ A` (macOS), `⌘ ⇧ A` (IntelliJ IDEA Classic (macOS)), `⌘ ⇧ P` (macOS System Shortcuts), `Ctrl+Shift+A` (XWin), `Ctrl+Shift+A` (GNOME), `Ctrl+Shift+A` (KDE), `Escape, X` (Emacs), `Ctrl+Shift+P` (Sublime Text), `⌘ ⇧ P` (Sublime Text (macOS)), `⌘ ⇧ A` (Xcode), `Ctrl+Shift+A` (Visual Studio), `⌘ ⇧ A` (Visual Studio (macOS)), `Ctrl+Shift+A` (ReSharper), `⌘ ⇧ A` (ReSharper (macOS)), `Ctrl+Shift+A` (QtCreator), `⌘ ⇧ A` (QtCreator (macOS)), `Ctrl+I` (NetBeans), `Ctrl+Shift+A` (Eclipse), `⌘ 3` (Eclipse (macOS)) and type `Import Tests from File`.

2. In the file system dialog that opens, select the `.xml` file with test results and click Open.

> **Note:**
> Import only works for the test results in `.xml` format.

## See also

### Getting Started

[Unit testing tutorial](unit-testing-tutorial.html)

### How tos

[Boost.Test](boost-test-support.html) [Catch](catch-tests-support.html) [CTest](ctest-support.html) [Doctest](doctest-support.html) [Google Test](creating-google-test-run-debug-configuration-for-test.html)