Determining the logistics of an Exploratory run
A frequently used term when discussing Rainforest Exploratory is 'scope'. In the context of Rainforest Exploratory, the scope of an Exploratory run is the whole of what is being tested in one Exploratory run. To determine the scope of an Exploratory run, there are 3 primary considerations: Exploratory resources, the object of testing, and level of coverage.
When determining the scope of an Exploratory run the first thing to consider are the resources allocated by Rainforest for the Exploratory run. Resources allocated for each Exploratory run are the same.
Exploratory testers work in teams of 4 and that same team of 4 testers will be sent to test your application each time you trigger an Exploratory run. These testers will each perform 4 hours of testing for a total of 16 hours of testing per run. These 16 hours of testing will occur at any time during the allotted 48 hour window that begins the moment a run is triggered.
The Object of Testing
The object of testing is what is actually being tested during that Exploratory run. Often, while Exploratory runs are constructed around testing a single object of testing such as a feature or portion of application, how the object of testing interfaces with the rest of the application is another important consideration.
Suppose, as an example, that a new feature 'A' is designated as the object of testing for an Exploratory run. Let's also suppose that feature 'A' functions primarily by interacting with features B and C. When approximating the scope of this Exploratory run, because feature 'A' functions via its interactions with these other features, how 'A' interacts with B and C is the actual scope of the Exploratory run.
In this hypothetical, while the intent of the Exploratory run is to "test the functionality of feature 'A'", the scope of this Exploratory run could encompass at least 2 test scenarios-- A interacting with B and A interacting with C.
Level of Coverage
When planning out an Exploratory run, a final consideration is the level of coverage for the object being tested. In the context of exploratory, coverage can be thought about as balancing between breadth and depth of testing. Depending on need, determining this balance between breadth and depth of coverage will be help in approximating the scope of an Exploratory run.
Using the example from before, the object of the run testing feature 'A' against features B and C was just 'test the interaction of feature A with features B and C'. This indicates to the tester team that breadth of testing of each tester would be spread portioned out evenly between both scenarios.
But imagine that out of the 2 primary features, the interaction of feature 'A' with features 'B' is more frequent and heavy than its interaction between 'A' and 'C'. When considering what the scope of the run should be, it may be of more value to test feature 'A' and its interactions with features 'B' in greater depth with a run, and then save testing between 'A' and both 'C' for a follow up run.
Alternatively, the run objective can specifically instruct the tester team to test 'A' against B and C but place a heavier focus on 'B'. This configuration of the run may strike a balance between both breadth and depth.
Pro-tip: Ask us for help if you're unsure of scope
With all these considerations to juggle, learning how to scope out Exploratory instructions can seem daunting. If you have additional questions or would like some advice, please reach out to firstname.lastname@example.org!