Exploratory Testing Techniques
Here are the 4 key techniques that any testers can refer to and use for their exploratory testing. Each component has its own strengths/weaknesses. Tester do not have to stick with a single component, but should spread out and make use of all of them or a combination of them. The trick is to know which one to choose and apply and when.
1. Freestyle
This is basically Ad-hoc testing. Hit the product from black box standpoint. From the customer’s perspective. Pros: Low cost. Anyone can do it. Encourage creativity. Cons: May not yield the critical bugs. Low quality bugs are typically found with lots of dupes. Difficult to determine coverage.
2. Scenario based
Using a pre-defined end-to-end scenarios, complete with actual reproducible steps and validation methods prior to testing. Testers can use these scenarios as the base, and figure out new end-to-end path that will achieve the same goals. Pros: Easy to trace the repro steps and follow. Can determine test coverage. Cons: Pre-defined scenarios may actually not represent what the customer really wants.
3. Strategy based
Testers do have some background of the product. Thoroughly understand the architecture and flow of the product. Tester can then leverage the product knowledge and combined with well-known testing techniques to go about testing. More to come on the techniques later. Pros: Test techniques are proven to be effective. Testers just need to master them and apply them in the right situation. Testers are also pretty much free to use their own instinct and creativity to go about testing the product. Focus on learning. Cons: Newer testers on the team may not have the sufficient experience or knowledge of the product to be completely effective.
4. Feedback based
Start out pretty much same as Freestyle testing. But as testing sessions are conducted, testers build up a history of test executions, areas covered, bugs identified, code churns, etc. Very similar to our session notes. Testing from historical data such as bug records, data from automations and scripts, application logs, customer reported issues, etc. Use these data as input so tester can identify which areas may yield the most bugs. Pros: Knowledge is not lost. Make use of previous knowledge is very powerful. Cons: Sometimes it’s very difficult to make use of existing data effectively (especially if there are a lot). May actually spend more time gathering and processing these data rather than actual testing.
Here are the 4 key techniques that any testers can refer to and use for their exploratory testing. Each component has its own strengths/weaknesses. Tester do not have to stick with a single component, but should spread out and make use of all of them or a combination of them. The trick is to know which one to choose and apply and when.
1. Freestyle
This is basically Ad-hoc testing. Hit the product from black box standpoint. From the customer’s perspective. Pros: Low cost. Anyone can do it. Encourage creativity. Cons: May not yield the critical bugs. Low quality bugs are typically found with lots of dupes. Difficult to determine coverage.
2. Scenario based
Using a pre-defined end-to-end scenarios, complete with actual reproducible steps and validation methods prior to testing. Testers can use these scenarios as the base, and figure out new end-to-end path that will achieve the same goals. Pros: Easy to trace the repro steps and follow. Can determine test coverage. Cons: Pre-defined scenarios may actually not represent what the customer really wants.
3. Strategy based
Testers do have some background of the product. Thoroughly understand the architecture and flow of the product. Tester can then leverage the product knowledge and combined with well-known testing techniques to go about testing. More to come on the techniques later. Pros: Test techniques are proven to be effective. Testers just need to master them and apply them in the right situation. Testers are also pretty much free to use their own instinct and creativity to go about testing the product. Focus on learning. Cons: Newer testers on the team may not have the sufficient experience or knowledge of the product to be completely effective.
4. Feedback based
Start out pretty much same as Freestyle testing. But as testing sessions are conducted, testers build up a history of test executions, areas covered, bugs identified, code churns, etc. Very similar to our session notes. Testing from historical data such as bug records, data from automations and scripts, application logs, customer reported issues, etc. Use these data as input so tester can identify which areas may yield the most bugs. Pros: Knowledge is not lost. Make use of previous knowledge is very powerful. Cons: Sometimes it’s very difficult to make use of existing data effectively (especially if there are a lot). May actually spend more time gathering and processing these data rather than actual testing.
