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