Jump to content

Ad hoc testing

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by 47.31.218.235 (talk) at 06:45, 15 July 2021 (added Types of Adhoc Testing Heading). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Ad hoc testing is a commonly used term for software testing performed without planning and documentation, but can be applied to early scientific experimental studies.

The tests are intended to be run only once, unless a defect is discovered. Ad hoc testing is the least formal test method[citation needed]. As such, it has been criticized because it is not structured and hence defects found using this method may be harder to reproduce (since there are no written test cases). However, the strength of ad hoc testing is that important defects can be found quickly.

It is performed by improvisation: the tester seeks to find bugs by any means that seem appropriate. Ad hoc testing can be seen as a light version of error guessing, which itself is a light version of exploratory testing.[citation needed]

Types of Adhoc testing

  1. Monkey testingMonkey 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.
  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 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.[1]

References

  1. ^ Rana, Kuldeep (2019-12-03). "Adhoc Testing - Definition, Advantages and Disadvantages". ArtOfTesting. Retrieved 2021-07-15.