Ad-Hoc Testing

Ad-Hoc Testing is the testing type which is performed without any proper procedure and without any Requirement Specification. Ad-Hoc testing is totally informal testing which have intension to break the application as early as possible and found important defect early.  In Ad-hoc testing tester do not have any test cases so only the users who have very high knowledge regarding the application only they can perform Ad-Hoc Testing.

In Ad-Hoc testing important defect found very quickly so this type of testing is also have importance. Also when our application is on deadline and team do not have enough time to test the application with proper documentation and test cases, Ad-Hoc testing is useful in that case. Ad-Hoc Testing will be effective only when tester have in depth knowledge about the application.

The bugs that are found during Ad-Hoc Testing are very difficult to reproduce because we do not have any proper test cases to reproduce that bug.

Ad-Hoc Testing Type

• Buddy Testing: In Buddy Testing, 2 members test the application together. In 2 members one from development team and other from Testing Team. They start testing together so for both it is good to develop the proper Test Cases and it is good to developer to fix the design issue earlier. This type of testing start after completion of Unit Testing.

• Pair Testing: In Pair Testing, 2 testers work on same machine to find out defects. Both can share ideas. One Tester will execute the Test Cases and other will write the records of finding issues.

• Monkey Testing: In Monkey Testing, Test the application without any goal. As name applies like Monkey moves tree randomly. No one know on which tree Monkey will move. The testing is like same. Tester test the application randomly without any proper guild line.