product

How to Organize Rainforest QA Tests with Features & Saved Filters

Picture of Otávio Dalarossa
Otávio Dalarossa, Tuesday November 14, 2017

More tests doesn’t always mean more coverage — in fact, we’ve found that utilizing a smaller group of tests strategically can be far more impactful than building a huge database. But whether you have 10 tests or 100 tests, a good test database is an organized one.

Fortunately for Rainforest users, we’ve added a few organizational tools to help keep test databases streamlined and execution running faster. Here are a few new features from Rainforest that will help you maximize the impact of test cases:

Grouping Tests by Feature

feature-blogpost

Rainforest lets you organize and view coverage progress by feature. Simply create a feature and start adding tests. You can easily add tests into features when you create a test, from the test view, or from the test list.

How to Group Tests by Feature

To create a feature, click the “+” button next to “Features” on the left nav menu and give your feature a name. Note that feature names should be unique to reflect your product structure. Because features are intended to reflect functionality that is unique to a part of your product, a test can only be included in one feature group at a time.

Tests can be added to features in several ways. When you create a test, simply select the feature you want to move it into using the drop-down from the 'New Test' modal. You can also create a new feature from here by dynamically typing it into the feature field. By design, a test can only be part of one feature.

Saved Filters

filters-blogpost

Saved Filters let you group and filter tests at a more granular level that can be customized to your organization’s needs. Saved filters can be useful for a few common use cases:

  • Draft tests – As you start drafting tests, tag them as #draft and create a saved filter with this view. Remove the #draft tag once it’s done. When used in this workflow, the "Draft” saved filter can act as your to-do list.
  • Archived tests – For obsolete or deprecated tests, it can be common practice to tag them as #archived, rather than delete them, and create a saved filter to view these tests.
  • Bugs – For known, existing issues, it can be helpful to tag the test with #bug and create a saved filter to aggregate all issues.

If you are organizing your tests into smoke and regression test suites, it’s generally recommended that you use Run Groups.

How to Use Saved Filters

To create a saved filter, click the “+” button next to Saved Filters and specify the tags you wish to filter by. Saved filters let you use advanced conditions to generate and you can add as many conditions as you’d like. To populate saved filters, add tags to tests to fulfill the saved filter condition and they will show up automatically.

There are 3 ways to run saved filters: - Click the “Run” button and select platforms to run your tests - Run from the CLI using the command rainforest run --filter 2343 or rainforest run --folder 2343 - Add a saved filter to a run group and trigger the run group To add a saved filter to a run group, click Run > Add to Run Group on the saved filter view.

Designing More Efficient QA Workflows

Streamlining your test database is just one step towards creating a faster, stronger and more efficient QA process. To learn more about how to customize your QA strategy to fit your product and your team’s needs, check out our webinar on rightsizing your QA strategy. Rainforest co-founder and author of the Continuous Testing Manifesto, Russell Smith, is joined by Rainforest Onboarding Specialist Maddie Blumenthal to share their best tips and tricks for creating the perfect QA strategy for your team.

Filed under: features, saved filters, and qa workflows