Structured Exploratory tests provide additional confidence of coverage, while allowing testers to still explore the application. This page has general guidelines on composing a structured exploratory test.
Naming
Keep the following style:
[Structured Exploratory][Main feature under test][Optional: Sub-feature under test] Description of the test
Structure
Start with an info step describing it is a structured exploratory test. This allows the tester to know what is expected from them. Use the following template text:
"This is a structured exploratory test. Please follow the guidelines on how to execute structured exploratory tests: https://support.testlio.com/support/solutions/articles/39000006891-execute-structured-exploratory-tests"
Add another info step for the Mission Statement and describe the goal of this test.
Keep the mission statement short (don’t list all coverage items).
Make sure the area to be explored and the main focus are clear.
Example: Ensure users can make changes to their preferences to check for UI changes based on the selection.
Area is preferences.
Focus is changes to UI based on preference changes.
Add an info step for Prerequisites
If the tester has to start testing from a specific state/page, describe that in the Prerequisites step.
To the Prerequisites step, add the information about the test execution time, this way testers will have a better sense of execution depth across steps presented in the test.
Test Steps
Use only pass/fail steps, not exploratory
Start steps with ‘Verify…’ and formulate a statement where describing that one can do the action:
Test describes the features to be tested, but does not specify how to perform actions.
There is no need to add Expected result as 'verify' already describes the intended outcome.
Tests could be written as logical user/business flows.
Divide positive and negative coverage into separate steps.
Hints can be given to testers on which scenarios to concentrate on
Since there is no dedicated notes field for the test step, include any relevant information in the Expected Result field as a workaround. There should be important details about the feature, such as multiple items to pay attention to, limitations, known issues, etc. Please avoid adding instructions on how to test.
Hints are not required for every test step.
Test Duration
Structured Exploratory tests should be aimed to be timeboxed between 5-15 minutes.
As a general rule, limit the number of steps in a single test to no more than 15.
Remember to include this information in the Prerequisites info step.
Examples
Instructions on Execution
You can see instructions for executing structured exploratory tests in the Support Center: https://support.testlio.com/support/solutions/articles/39000006891-execute-structured-exploratory-tests