Adhoc Testing

Hello friends! in this post we will be learning about - Adhoc testing. As the name suggests Adhoc testing is an informal and unstructured way of testing any application. The main aim of Adhoc testing is to uncover the defects which are otherwise not found by following normal testing process.

Adhoc testing definition

Adhoc testing is a type of testing which is performed without any planning and documentation. It is unstructured, unplanned and informal testing performed after following the formal testing processes in order to break the system and find the defect which might not get caught by following usual testing approach.


Features of Adhoc testing

  1. It is unplanned and unstructured.
  2. It doesn't require any documentation or formal test case execution.
  3. It is usually performed after completion of formal test case execution.

Types of Adhoc testing

  1. Monkey testing - Monkey testing is a type of testing that is performed with an intent to break the system by passing random input and following random work-flows.
  2. Buddy testing - Buddy testing is a type of testing in which a developer and a tester work together to test the application, thus improving the testing process with the developer's internal architecture knowledge and testing mindset of the tester.
  3. Pair testing - In case of Pair testing two testers work together to perform testing with wider and better test coverage. One tester can perform testing and the other tester can observe and analyze the testing process.

Advantages of Adhoc testing

  1. Because of the independence of not following any testing process, tester can find hidden defects which can get missed while following conventional testing approach.
  2. Adhoc testing approach like buddy testing, pair testing improves test coverage with the use different mindset of QA-QA and QA-Developer pairs during testing.
  3. It takes very less time to execute as there is no planning and formal documentation of testing artifacts.

Disadvantages of Adhoc testing

  1. Since it is adhoc and unstructured, so bugs if found are very hard to reproduce.
  2. We cannot trace the requirements or check requirement/test coverage, as there is no traceability matrix or any documentation for that matter.
  3. Efficiency of testing is dependent on the skill of tester as well as the prior knowledge of the system. It is because of the fact that Adhoc testing requires a lot of error-guessing which requires skills and prior knowledge.