Best Practices

Adding tags to tests helps you manage and organize your test suite in Rainforest. Filter tests using tags to make them more discoverable. Tags are effective for managing groups of related tests. Below are several tag categories that have proven effective for organizing test suites.

Test Complexity

When writing Visual Editor tests, tag them based on the type of QA testing you are doing.

• Smoke. These are the most critical workflows. They usually occur on a regular cadence and should be run with every new release.
• Regression. These are more detailed tests that spread across a large part of your application or website. Write these tests after you have begun running your smoke tests.

Test Type

If your application or website runs on multiple platforms, separate your tests by platform type.

• Web and Mobile. For applications with different web and mobile workflows, tag tests appropriately and run them whenever there are updates to the workflows.
• Product or Feature. Adding a project-based tag helps to organize your tests. This is especially useful when building out a regression suite or creating tests for new platform features. We recommend picking one name per project, feature, or area and tagging all tests related to that area with the name.

You can organize a test by including it in a feature. For more information, see Organizing Tests by Feature.

Test Status

When onboarding new team members, adding a status tag is helpful, especially when there is an approval process for new tests. Examples include:

• To Be Reviewed
• In Review
• Reviewed

Bugs

For known issues, tag tests as #Bug. Then, create a saved filter to aggregate all issues.

Maintenance

• Keep tags up to date. If a tag such as “June release” is no longer valid, delete it from your account settings. The tag is automatically removed from all tests.
• We recommend not deleting tests but rather tagging them with #Archive and setting them to disabled.

If you have any questions, reach out to us at [email protected].