Hello friends! in this post, we will be learning about – adhoc testing. As the name suggests it 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 the 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.
We perform this after following the formal testing processes. In order to break the system and find the defect which might not get caught by following the usual testing approach.
Features of Adhoc testing
- It is unplanned and unstructured.
- It doesn’t require any documentation or formal test case execution.
- We usually perform this after the completion of formal test case execution.
Types of Adhoc testing
- Monkey testing – Monkey testing is a type of testing that is performed with the intent to break the system. The tester performs this by passing random input and following random work-flows.
- 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.
- Pair testing – In the 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
- Since there is no mandate of following any testing process, the tester can find hidden defects. These types of defects would otherwise get missed while following the conventional testing approach.
- Techniques like buddy testing, pair testing improves test coverage with the use of different mindsets of QA-QA and QA-Developer pairs during testing.
- It takes very little time to execute as there is no planning and formal documentation of testing artifacts.
Disadvantages of Adhoc testing
- Since it is adhoc and doesn’t follow any structure. So the bugs if found are very hard to reproduce.
- We cannot trace the requirements or check requirement/test coverage, as there is no traceability matrix or any documentation for that matter.
- The efficiency of testing is dependent on the skill of the 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.
That’s all I have in this post. Feel free to ask any questions in the comments. Check out the complete software testing tutorial here.
Kuldeep is the founder and lead author of ArtOfTesting. He is skilled in test automation, performance testing, big data, and CI-CD. He brings his decade of experience to his current role where he is dedicated to educating the QA professionals. You can connect with him on LinkedIn.