Other Features for Test case Design

Multiselection for Tests

The Multiselection feature on the Tests page allows users to perform bulk actions on multiple tests, entire test suites, or folders.

To enable Multiselection:

1. Click the Multiselection button located at the top left corner of the Tests page.

   

2. Select the desired tests, test suites, or folders.

3. Once selected, the Multiselection options toolbar will appear at the bottom of the page.

   

---

Available Multiselection Actions:

1. Run – Launches a test run containing the selected items.

2. Labels – Add or remove labels or custom fields for the selected tests.
   Learn more about labels →

3. Copy – Copy selected tests within the current project or to another project.

4. Move – Move tests to another test suite or folder within the same project.

5. Tags – Assign existing tags or create new ones for the selected tests.
   More on using tags →

6. + Link – Open a pop-up to link a related defect to the selected tests.

7. Priority – Set priority levels for the selected tests.

8. More options (⋯) – Contains additional action Download – Export selected tests to a spreadsheet.

9. Delete – Permanently remove the selected tests.

URL/ID Quick Copy

Depending on your needs, you can set up a convenient way to copy URL/IDs in Test Cases, Suites and Runs.

To start, you need to open a Test Case (Suite or Run):

1. Click the copy icon to open the modal window.
2. In the window that opens, you can copy the format you are interested in.
3. Turn on the toggle next to a format if you need to use it frequently.
4. Now, every time you click on the ID, the selected format will be copied to clipboard without any further actions.

Suites and folders

Unlike other test management systems, Testomat.io doesn’t allow suite to include other suites and tests. That’s why you can either create a suite (a collection of tests) or folder (collection of suites).

When creating a suite you have to explicitly set its type: a suite or a folder.

This was designed so tests structure could match the filesystem. For instance, if you use BDD project, feature file can contain scenarios, but can’t contain other feature files. The same for automated tests, a file can contain tests but can’t contain other files.

It’s assumed that in any moment a manual test can be automated, so it is important to keep the filesystem structure in a project.

An empty suite can be converted to folder or vice versa

Also you can set an emoji icon for the suite

If your test is deeply nested within suites and folders, you can use breadcrumbs with tooltips to navigate the project structure more effectively.