Ad-hoc VS exploratory testing
Ad-hoc testing will be done in any stage of testing even we can do while unit testing but exploratory testing
generally done after acceptance testing .We can say ad-hoc testing is a part of exploratory testing.
Both will be performed when lack of time and resource and both will be done by experienced tester
who is having a domain as well as good testing experience.ad-hoc testing done in structure and well
define test technique but exploratory testing will be doing after agile practicing. Exploratory testing concept
comes after agile and scrum comes.ad-hoc is a commonly used term for software testingperformed without
planning and documentation. The strength of ad hoc testing is that important defects can be found quickly
or in initial stage. But exploratory testing is based on usability, UI, Functional and boundary analysis.
Exploratory testing seeks to find out how the software actually works, and to ask questions about how it
will handle difficult and easy cases. The quality of the testing is dependent on the tester's skill of inventing
test case and finding defect. Another benefit is that, after initial testing, most bugs are discovered by some
sort of exploratory testing. This can be demonstrated logically by stating, "Programs that pass certain tests
tend to continue to pass the same tests and are more likely to fail other tests or scenarios that are yet to be
explored." Freestyle exploratory test ideas, when revisited, are unlikely to be performed in exactly the same manner,
which can be an advantage if it is important to find new errors or a disadvantage if it is more important to repeat specific
details of the earlier tests. Exploratory testing is testing of unfamiliar applications. The test scripts would not be prepared beforehand.
Test case design and execution are done concurrently. Ad-hoc testing is intended to look for defects randomly.
This can be carried out by any one by Exploratory testing is a thoughtful approach and driven by logic. It is an intellectually
challenging process where one is
limited by one's own imagination and understanding of the software being tested. It provides enough scope to extend
the reach of testing to certain areas that cannot be easily accommodate test cases.
Ad hoc testing the product without following any Test specifications by following functionality of the
Products. It’s done by domain experts.
Exploratory testing the product without following any test specifications and without following Functionality.