Adhoc Tests are done after formal testing is performed on the application. Ad-hoc methods is not a structured approach, it is not scripted and documented. Hence, defects found using this method are hard to replicate as there are no test cases aligned for those scenarios.
In Adhoc testing, the knowledge of the tester about the application may the critical thing and the tester tries to break the application randomly. Hence, the success of Adhoc testing depends on upon the capability of the tester, who carries out the test. The tester has to find defects without any proper planning and documentation, solely based on tester’s intuition.
When to perform Adhoc Testing
Ad-hoc testing can be performed when there is limited time to perform testing. Usually, ad-hoc testing is performed after the formal test execution. Ad-hoc testing will be effective only if the tester is knowledgeable of the System Under Test.
Types of Adhoc
Buddy Testing : Two buddies, one from the development team and one from test team mutually work on identifying defects in the same module. Buddy testing helps the testers develop better test cases and development team can also make design changes early. This testing usually happens after unit testing completion.
Pair Testing : Two testers are assigned the same modules and they share ideas and work on the same systems to find defects. One person can execute the tests and another person can take notes on the findings. Roles of the Tester can be a tester and scriber during testing.
Monkey Testing : Randomly test the product or application without test cases with a goal to break the system.