Adhoc testing is an informal and random type of software testing performed after formal testing to find any loopholes in the system. Also known as Random or Monkey testing, Adhoc testing is not based on any methodological approach, making it a type of Unstructured Software Testing.
Types of Adhoc Testing
- Buddy Testing: Involves a developer and a tester working together to test a module using random inputs.
- Pair Testing: Two testers work on the same module, with one performing random tests while the other records findings.
- Monkey Testing: The system is tested with random inputs and monitored for functionality without using test cases.
Characteristics
- Performed randomly.
- No documentation, test cases, or test designs.
- Done after formal testing.
- Unstructured testing approach.
- Takes less time than other testing techniques.
- Good for finding bugs and inconsistencies not covered by test cases.
When to Conduct Adhoc Testing
- Limited time for system testing.
- No clear test cases to test the product.
- Formal testing is completed.
- Development is mostly complete.
Advantages
- Identifies errors not found with written test cases.
- Can be performed within a limited time.
- Helps create unique test cases.
- Builds a strong, less problem-prone product.
- Can be done anytime during the Software Development Life Cycle (SDLC).
Disadvantages
- Resolving errors can be difficult due to a lack of written test cases and documents.
- Requires good product and testing knowledge to identify issues effectively.
- No assurance that errors will be found.
- Uncertain time frame for finding errors.
Best Practices
- Good software knowledge.
- Identify error-prone areas.
- Prioritize test areas.
- Create a rough test plan.
- Use the right tools.
Find more in our blog.
