Local TMS is a lightweight and agile way to store and manage your test data well suited for teams regardless of their size. Local TMS stores test data as a collection of t.md and r.md files right in the project. This approach allows for branching, versioning, reviewing, and better integration with automated tests.
Take a look at this short video to see how local TMS works:
warning
Local TMS format is experimental and does not have a specification, therefore, it is subject to changes in future releases.
Enable local TMS
Press CtrlAlt0S to open settings and then select Tools | TMS.
Set the Markdown checkbox under TMS.
If your project already has any t.md files in it, they will be displayed in the Markdown tab of the TMS tool window.
Create a test suite
In the Project tool window (Alt01), select the directory in which you want to create the test suite, press AltInsert, and select Test Suite from the menu.
Alternatively, right-click the directory and select New | New Test Suite.
Give the test suite a name and press Enter.
Test suite files have the following format:
# MyTestSuite
Tags: tag1, tag2
Meta: key1 = value, key2 = value
## S1 Sub-suite 1
* C1 Test Case 1
Tags: tag3
* Step 1
* Step 2
* C2 Test Case 2
Tags: tag4
* Step 1
* Step 2
## S2 Sub-suite 2
* C3 Test Case 3
Tags: tag5
* Step 1
* Step 2
The heading contains the test suite name.
Tags and metadata are specified using Tags and Meta keywords right after the element declaration. Tags and metadata can then be used as criteria for filtering TMS items.
Each element (suite, sub-suite, and case) can have its own tags and metadata.
Tags and metadata are inherited from a suite or a sub-suite to its respective test case(s). Inherited tags and metadata are shown for the test cases in the TMS tool window.
List items are test cases.
Letters S and C followed by numbers represent an ID assigned to a test suite or case. Assigning an ID for the test case is recommended, and optional for the test suite.
Nested list items are test steps.
note
When assigning an ID to a test suite or case, specify only the number. The corresponding letter is added automatically.
tip
Rename refactoring ShiftF6 and find usages AltF7 work for all identifiers and metadata in local TMS files. This is useful, for example, when you want to consistently rename an element that might be used elsewhere, or quickly look up occurrences of test statuses, user ids, tags, and so on.
Create a test run
Test runs are stored in r.md files as part of your project. They are not required to correspond to a test case and can consist of arbitrary steps.
In the Project tool window (Alt01), select the directory in which you want to create the test run, press AltInsert, and select Test Run from the menu.
Alternatively, right-click the directory and select New | New Test Run.
Select the test cases that should be checked during this test run.
Manage a test run
For each test case in a test run, you can specify its outcome and who performed the test.
Go to the test run file.
Specify the result, for example, [ok] or [fail] and the agent id using the @ sign, for example:
* [ok] @my.user Test Case 1
Share test data through VCS
Test data stored in local TMS can be shared and versioned just like any other project files.
For more information about enabling and using version control in your project, refer to Version control topic.
Thanks for your feedback!
Was this page helpful?
Cookie Settings
Our website uses some cookies and records your IP address for the purposes of accessibility, security, and managing your access to the telecommunication network. You can disable data collection and cookies by changing your browser settings, but it may affect how this website functions. Learn more.
With your consent, JetBrains may also use cookies and your IP address to collect individual statistics and provide you with personalized offers and ads subject to the Privacy Notice and the Terms of Use. JetBrains may use third-party services for this purpose. You can adjust or withdraw your consent at any time by visiting the Opt-Out page.