Adding tags to tests helps you manage and organize your test suite in Rainforest. You will be able to filter the tests by these tags, and find tests more easily!

When you're ready to run a suite of tests, you can view and run tests by tag from the Rainforest Dashboard.

Commonly used tagging schemes to keep track of your tests

Tags are an effective way to manage groups of related tests. Below are several categories of tags that have been effectively utilized to organize test suites:

Complexity of Test

When you begin writing Rainforest tests, we suggest you start by tagging tests based on the type of QA test they are.

  • "Smoke" - Smoke tests are your most important workflows. They are usually run at a regular cadence and should be run with every new release.
  • "Regression" - Regression tests are more detailed tests that spread across a large part of your application or website. You should write these tests after you have begun running your smoke tests at a regular cadence.
  • "Stub" - Using embedded tests as building blocks for your tests cuts down on time and typing. Marking the original embedded tests as stub tests mean you can exclude them from runs and smart folders, therefore not wasting steps.

Type of Test

Depending on your platform, you may want to separate out different types of tests. We suggest tagging these tests by the type.

  • Example: Web and mobile - For tests that have a different flow on web than mobile, tag tests separately and run when updates are made to the different flows.

Product or Feature

As you are building out your regression suite and create tests for new features or areas of the platform, adding a tag for a project will help you organize the tests. We suggest picking one name per project, feature, or area and tagging all tests related to that area with that name.

You can also assign tests to features wherever applicable while you write them using our new "Features" capability. Find out more about our new "Features" capability here.


As you onboard more members of your team, adding a status tag can be helpful if your tests, especially when there is an approval process for new tests. Tags can easily be added and deleted in large batches so you can update them as tests are reviewed.

  • Example: To Be Reviewed, Reviewed

How to use the tagging system

Add tags as you're writing out your tests or you can perform a bulk test tagging by selecting tests from the "All Tests" page. Consider using tags that describe a particular:

  • Feature, workflow, or functionality; these are best organized into a Feature
  • Platform or project; these are best organized into a Run Group

How to add a tag

Click into any test and there is a "Tags" field in the test settings sidebar to the right. Start typing and hit Enter to create your tag. Please note that Tags are case sensitive. You can add multiple tags to each test.

How to add Tags to multiple tests at once

In the list of tests, click on the checkbox at the left of all the tests you want to add a tag to. Click on "Tag Tests" and then select the tag you wish to use or create a new one by typing it into the tag field and hit Enter to tag the tests.

How to modify or delete Tags

When you're viewing a test on the test writing page, click the 'x' on the tag to remove this tag from the test. Your test will no longer show up when you search for tests by tag, nor when you run your tests by tag.

You can also change the name of your tags or delete them completely from your tests in Settings. When the tag is edited or deleted, it will be edited or removed from all the tests it was added to.

Did this answer your question?