The 4 essential (1 optional) requirements of Exploratory Instructions
Now that you're ready to begin utilizing Rainforest Exploratory testing, the first thing to master is defining the key requirements of each Exploratory run. Each of the following are defined as requirements because these are absolutely necessary for each Exploratory run to be triggered and executed successfully. The 3 key requirements are as follows:
- At least one (1) functioning URL
- Site authentication credentials and/or test accounts
- An overview of the objective of the run
- Any areas of your application to void
1. At least one (1) functioning URL:
For any Exploratory run to be executed successfully, at least (1) functional starting URL must be provided to your Exploratory testing team. The tester team will treat this URL as their starting point from which they should begin their testing.
In the Exploratory instruction form, the starting URL can be inputed in the text field below
Are there specific URLs you wish to cover :
*Note: If your site is restricted by IP address, please notify Rainforest of this before starting your exploratory run.
2. Site authentication credentials and/or test accounts
In the same vein as the above, it is also necessary to provide to testers any authentication credentials that may be needed to access the defined testing site. For some sites, this involves inputting authentication credentials upon navigation to the testing site to gain access. For others, the testing site can be navigated to, but the actual areas of testing may be gated by logging in as a specific user into an predefined state.
We recommend that all authentication credentials and/or test accounts be recorded in the field below
If Testers need to log in, please provide login credentials below in the Exploratory instruction form:
3. An Overview of the Objective of the Run
While setting the objective of "Build my test suite" or "Find Bugs" will provide some general direction about the objective of the Exploratory run, further elaborating on the round provides the tester team with context to better execute the run and return only meaningful results.
Overviews can be as high level or as granular as you want them to be. Some give a brief summary of the feature being tested; others will provide a comprehensive report about how a feature is supposed to function.
Areas of focus are portions of your website that are functionally related. These may include specific features and workflows. Please be sure to avoid using any internal language to describe any product areas of focus.
To gauge what level of detail is appropriate for your run, check out our Best Practices for Writing Exploratory Instructions!
The overview should be input into the field below "Are there Areas of Focus for this Test Session?" like the example below:
4. Any Areas of your application to avoid.
Testers will not cover any areas specified in the section
Which parts of your application should testers avoid?. This often includes areas that have known issues or specific features and workflows that are being deprecated.
As each Exploratory run is unique, it will take some time to learn how to calibrate these requirements for each run. If you have any questions, please shoot us a message at email@example.com!