Write, organize and run your initial test suite

When building out your smoke tests, focus on developing test cases of critical importance, that are repeatable and easy to interpret, so you can ensure your tests consistently return valuable feedback.

Consider any instructions you might need to repeat across different tests—these may be complete processes, like a login to access your app, or a repeating portion of a process, like the steps for filling out a form.

A checklist for building your essential functional test case checklist can be found here.

1. Write your Smoke Tests

Foundational tests like smoke tests are crucial in testing that the basic functions of your site work. When instructing testers to perform a series of test cases, follow the Rainforest Action / Question format in each step.

Steps are the primary means of instruction to your testers, so it's important to write steps as clearly and as effectively as you can. Each step is comprised of an action and a question to guide testers through what they should do:

  • Action - What should the tester do?
  • Question - In the form of a Yes or No question.

This simple format allows you to validate each essential action in a flow, tracking success or failure each step of the way.

Useful functions you can perform on a step: 

  1. Copy steps into another test
  2. Extract steps as an embedded test into a new test
  3. Move the order of the step within a test

2. Organize your tests

Select multiple / all tests to see additional options to duplicate, change browsers, tag tests, and delete.

By Tags

Apply tags to organize and categorize your tests as you're writing them out. You can later run tests by tag or filter them by tag from your Rainforest Dashboard. For example, you could include a "critical" tag for tests that need to be run every time you deploy or a "photos" tag for your tests related to the photos functionality in your app. To tag a test, start typing in the TAGs box and hit Enter to save the tag. You can also apply tags to multiple tests from the Tests page after selecting the appropriate tests.

By Features 

Rainforest Features lets you organize and view coverage progress by feature. Simply create a feature and start adding tests. You can also run your tests inside a specific feature, e.g. if you wanted to test several checkout flows.

By Saved Filters 

Rainforest Saved Filters provide a more granular way to organize your tests. You can define what tests should be included in a Saved Filter by adding a 'Tag condition'. A tag condition could be as simple as: “Include all tests with tag ‘green’”, or “Exclude all tests with tag ‘red’”.

3. Run your tests

Rainforest tests can be run as a single test run or multiple tests at a time. You can trigger test runs via our UI, which is demonstrated here, or via our API or CLI!

4. Optimize your tests

Once you've written and run a few tests, you - or our testers - will likely notice instructions or questions that need a bit of tweaking for clarity. This is a normal part of the test writing process, especially during the first few runs!

Working with our API? You can do all of the above programmatically! Learn more here.

Did this answer your question?