Test case testing vs Exploratory Testing
So which one is better? Easy answer. You need to do both types of testing. No this is not a case of just doing more is better!! Exploratory testing and test-case based testing take different and complementary approaches for testing a product. Let’s start with basic definitions.
Test case-based testing In this approach the test team sits down and defines the test cases that they will be carrying out on the day of regression. Here is the definition from softwaretestingfundamentals.com
“A test case is a set of conditions or variables under which a tester will determine whether a system under test satisfies requirements or works correctly.”
Typically the test case will have a series of steps with or without data being entered defined with one or more validation steps carried out to determine that the behavior of the system is occurring correctly.
Exploratory testing
In Exploratory testing the team sits down prior to testing of the next build and creates a charter or a set of guidelines on where to explore. This can include high defect areas, new feature areas, areas where defects are fixed etc. Here is a more formal definition from ISTQB
“Exploratory testing is a hands-on approach in which testers are involved in minimum planning and maximum test execution. The planning involves the creation of a test charter, a short declaration of the scope of a short (1 to 2 hour) time-boxed test effort, the objectives and possible approaches to be used.”
In addition if you are looking for an excellent guide on how to perform Exploratory testing Elisabeth Hendrickson’s book Explore It!! is an easy yet phenomenal read. Click to read more about this blog : Test case testing vs Exploratory Testing