Requires GOOD knowledge of the domain. The testing is conducted by the individual tester who has good knowledge of the domain.
| Tester overcomes the LACK of domain knowledge during the test design phase. The tester gains knowledge during the knowledge sharing sessions by subject MATTER experts.
|
It is more of a mindset
| Scripted testing is a formal testing methodology
|
It is suitable when requirements and specifications are not clear
| It is suitable when requirements and specifications are clear
|
Works well when the requirements change frequently
| Doesn’t work well when the requirements change frequently
|
Testers use logical reasoning to guide future testing.
| Testers follow step-by-step instructions and discourage deviations.
|
Testers feel more involved in exploratory testing
| Testers don’t feel involved as they have to follow step by step process
|
Bugs are detected quickly
| Bugs can be detected only at the end-of-life test cycle
|
Dependent on the skills of tester
| As the tester MUST follow the step-by-step process it is independent of the tester's skills
|
Effective when the testers are skilled
| Highly effective if the aspects and values that need to be TESTED are in sequence
|
Testers can change the test cased on the fly
| Testers have to follow a sequence test case in advance that are designed.
|
Testing is performed on the fly and hence test cases cannot be tested well in advance
| Test cases are prepared and reviewed well in advance.
|
There is no way to confirm that all requirements are met and implemented
| At the end of the testing life cycle the tester can confirm that all the requirements are met.
|
Repeating the same test becomes challenging as no documentation is created during exploratory test.
| The same tests can be repeated as the test scripts are defined in well advance.
|
Exploratory tests cannot be automated
| Scripted tests can be automated
|
Testers are not aware what to expect at the end of testing cycle
| Testers are aware what to expect at the end of testing cycle
|
