How Teams Use Rainforest Exploratory Testing
Exploratory testing on Rainforest is a great way to leverage our team of testing experts to get even more from our partnership. It’s a very flexible way to test features or get tests written in Rainforest. Minimal effort on your part and the results from these runs will help you to increase coverage and feel more assured that you’re not pushing buggy code that will negatively impact your customer’s experience.
We talked to our Customer Success team to get their thoughts on where clients have seen the most impact from Exploratory testing with Rainforest, and here’s what they had to say!
There are two basic functions of an exploratory test run: a bug bash and a test writing session. Below, we go into some of the benefits of each.
Using Rainforest Exploratory for Bug Bash
Feature-based: Whether more testing is needed on features that don’t have a lot of coverage, or if you’re developing a new feature and don’t have the time to put together full test cases, Exploratory testing is a great way to get coverage with little effort on your part!
- Uncovering issues while developers are still close to the code
- The logs that are generated (based on bugs that are found) from this session can be used as regression tests in the future
Release-centric: About to release a new feature that you’ve already tested, but want some more assurance that you not pushing a feature to generally available with bugs in it? This is another way to use Exploratory testing.
- Uncovering edge cases
- What will your end users encounter while using the feature if live?
- A quick temperature check as to whether or not it’s ready to be customer-facing
- You and your team could be “too close” to the code, and want other more objective eyes on it
Need some objective feedback on your UI or User Flow? Just ask!
Using Rainforest Exploratory for Test Writing
Strapped for time but need to get smoke or regression coverage for a new feature? Developing a new feature and have test plans? This is a great use for exploratory testing. Our team will do the heavy lifting of drafting test cases while you work on other aspects of your role. At the end of the test writing session, you’ll have a near-operational suite of tests. They usually require some finishing touches on your end, but for the most part you’ll be able to review, categorize and run these as part of your smoke or regression test suites.
It’s a best practice to run a bug bash exploratory run first, before asking the team to test write for you. The team is dedicated to you and gets better each time they work on a run. In order to maximize their knowledge of how your site works (and therefore be able to jump right into test writing) start with a bug bash if you’re interested in this option.
Exploratory Testing in Action
To see what using Exploratory with Rainforest looks like in action, check out our case study with Poll Everywhere, who uses Rainforest Exploratory to discover bugs on new features and determine where they should build out test coverage to have the greatest impact on product quality.
Getting Started with Rainforest Exploratory
Want to get started, or need more information about other benefits of Exploratory testing on Rainforest? If you’re already a Rainforest user, talk with your CSM – they’re able to help you figure out the best way to solve your QA problems and make sure that you get the most from our partnership!