When to conduct Adhoc testing
- When there is limited time in hand to test the system.
- When there are no clear test cases to test the product.
- When formal testing is completed.
- When the development is mostly complete.
Adhoc Testing in Software
Prerequisite – Software Testing
Adhoc Testing :
Adhoc testing is a type of software testing that is performed informally and randomly after the formal testing is completed to find any loophole in the system. For this reason, it is also known as Random or Monkey testing. Adhoc testing is not performed in a structured way so it is not based on any methodological approach. That’s why Adhoc testing is a type of Unstructured Software Testing.
Adhoc testing has –
- No Documentation.
- No Test cases.
- No Test Design.
As it is not based on any test cases or requires documentation or test design resolving issues that are identified at last becomes very difficult for developers. Sometimes very interesting and unexpected errors or uncommon errors are found which would never have been found in written test cases. This Adhoc testing is used in Acceptance testing.
Adhoc testing saves a lot of time and one great example of Adhoc testing can be when the client needs the product by today 6 PM but the product development will be completed at 4 PM the same day. So in hand only limited time i.e. 2 hours only, within that 2hrs the developer and tester team can test the system as a whole by taking some random inputs and can check for any errors.