Finding your way around Rainforest Exploratory

To get to the Exploratory page, click the "Exploratory" icon will appear in the navigation bar in the Rainforest Dashboard. 

From this page, you will be able to kick off runs, track your Exploratory history, and view the results from previous Exploratory runs. To learn how to start an exploratory run, visit this link!

By clicking into the title of a past run, you will be able to see the instructions you inputted for that particular run, including URLs to cover, login credentials and which areas to focus on or avoid.

To view the results of a particular run, which were added as Rainforest test cases, click the blue "View Tests" button.

Then you'll see a list of all the tests generated from that run.

Tips for organizing your Exploratory test cases

As Exploratory is run more and more, the number of test cases generated will inevitably grow. Below we've shared some proven best practices for how to handle bug-finding test cases after they've been logged.

Run the folder of newly documented tests

One of the easiest ways to manage newly documented bug-finding test cases is to run these tests to verify the bugs. As all test cases are written with the expected result in mind, the entire folder should fail, verifying the bugs documented by each test case. If you have your run failure integrations in place, your team will automatically be notified and can begin your bug triaging process seamlessly.

Tag or title the test with the priority level of the identified bug

When bugs are identified, change the priority of the tests to allow the results to be communicated efficiently across your team. By clearly identifying which bugs are more critical than others, you can provide your team with an order to follow when they address the bugs found by Exploratory.

Incorporate critical bug-flows into the regular regression suite

We recommend adding the more important and critical test cases to run as part of your regular regression. As these test cases are written with the expected result in mind, they can be run to ensure that such critical bugs are not recurring.

Tag tests with the name of the tested feature

Tagging exploratory generated test cases with the name of the feature is a simple way to bridge the gap between bug-finding and test-creation runs. Feature name tags can also be used to organize these tests in a smart-folder devoted specifically to the feature, making it easy to comprehensively test out a feature in Rainforest.

If you don't have access or have any questions about the Rainforest Exploratory UI, shoot us a message through Intercom (blue chat icon) at the bottom right or reach us at

Did this answer your question?