Adhoc testing is done when the testers do not have enough time at hand to do a detailed testing with proper test plans and test cases. Sometimes Adhoc testing is carried out at the end of the project after the execution of all the test cases. So in that sense Adhoc testing is the kind of testing which acts as a complement to other types of testing.

The success of Adhoc testing depends upon the capability of the tester who carries out the test. The tester has to find bugs without any proper planning and documentation solely based on just his intuition.

An important advantage of Adhoc testing is that it helps to save a lot of precious time. Sometimes it셲 after spending valuable time on preparing and explaining tests that the program셲 design is changed. With Adhoc testing precious time is not wasted on planning and documents.


  1. Be well prepared. Read a lot about defects from other projects. This will prepare the testers to detect bugs that would have gone unnoticed.
  2. Create a rough draft. Create a rough draft and NOT a detailed plan containing details like what to test, how to test and what problems to look for.
  3. Test in sessions. Test the application or software part by part i.e., one functionality at a time. This provides better focus and understanding of the problems, if any.
  4. Target key areas. Target those areas that have not been covered, in detail, in the test designs or user documentation.
  5. Learn to use different tools. At times certain defects may be brought to light by debuggers, profilers, and task monitors. So a thorough knowledge about these tools can make matters easy for the testers.
  6. Record your findings. Make a record of what bugs you found, where in the application they appeared, and the function. These records helps the developer and also testers of future applications. Also record what bugs you didn't find. That may seem odd, but there needs to be a record of what worked.
Share
Related Documents
  1. Are "Ad-hoc" Testing and "Ad Hoc" Testing same? (1683)
  2. Measurement of Ad-hoc Testing (1834)
  3. Tips for adhoc Testing (2634)
  4. Exploratory Testing (2481)
  5. Ad-hoc testing vs Exploratory testing ? (4750)
  6. Ad Hoc Software Testing (2684)
  7. The Nature of Exploratory Testing (2156)
  8. Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design (5029)
  9. Exploratory Testing - Risk-Based Agile Testing (4105)
  10. [Ebook] Exploratory Software Testing (5054)
  11. Context driven testing + Risk based testing (3310)
  12. Exploratory Software Testing (1741)
  13. Mocking and exploratory testing (1900)
  14. Exploratory Testing: Finding the Music of Software Investigation (2154)
  15. Exploratory Testing Dynamic (1788)
  16. Mobile Application Testing (14209)
  17. Exploratory testing (1445)
  18. Exploratory Software Testing (1064)
  19. Web Testing: Complete guide on testing web applications (5744)
  20. WebSite Cookie Testing (3368)