Chunks of Adhoc Testing

1.Ad-hoc word itself implies not methodical. Ad-hoc testing is the form of black block testing.

2.Ad-hoc testing is a part of Exploratory testing, which does not have any methods or boundaries.

3.It is done without any pre-planning or proper documentation.

4.The best time of doing ad-hoc testing is when tester exploring the application for better understanding of all the flows in the application which includes negative as well as positive scenarios as it helps us to find defects earlier or when user have thorough knowledge of the application so that he/she can find defects which could not be found through formal process

5.Most of the negative scenarios are executed while doing ad-hoc testing as there are no limits or boundation on testers.

6.Ad-hoc testing offers freedom to the tester to apply their own better approaches for testing the application which encourages them to discover more number of defects contrasted with the formal testing process.

7.Ad-hoc testing is not only useful for the tester to find defects, it is useful for developers as well.  The developer can do ad-hoc testing while developing their module , so that they can code in more appropriate and better way.  

8.The main trick of Ad-hoc testing is that user can test the main functionality of the application in just one flow by touching all the important modules, as the scenario is not documented so there is no focused testing and user have to create the scenario and keep the scenario in his mind only but at the same time this also becomes the drawback of ad-hoc testing as sometimes it becomes difficult for the testers to recall the executed scenario

9.One of the drawbacks of ad-hoc testing is recreation of the bugs sometimes become very problematic

10.Ad-hoc testing can only be done by skilled testers and not by new joiners in testing as the testers need to categorize and prioritize the scenario and the features which can be done by skilled testers more appropriately