Inscrivez-vous ou connectez-vous pour rejoindre votre communauté professionnelle.
The "Adhoc Testing" does not follow any structured way of testing and it is randomly done on any part of application. The aim of this testing is to find defects by random checking. Adhoc testing can be achieved with the testing technique called Error Guessing. Error guessing can be done by the people having enough experience on the system to "guess" the most likely source of errors.
The "Adhoc testing" is usually an unplanned activity also an informal testing type with an aim to break the system. This testing does not follow any test design techniques to create test cases. In fact is does not create test cases altogether. This testing is primarily performed if the knowledge of testers in the system under test is very high. Testers randomly test the application without any test cases or any business requirement document.
This testing requires no documentation/ planning /process to be followed. Since this testing aims at finding defects through random approach, without any documentation, defects will not be mapped to test cases. Hence, sometimes, it is very difficult to reproduce the defects as there are no test-steps or requirements mapped to it.
When execute Adhoc Testing?
Adhoc testing can be performed when there is limited time to do elaborative testing. Usually adhoc testing is performed after the formal test execution. And if time permits, adhoc testing can be done on the system). Adhoc testing will be effective only if the tester is knowledgeable of the system under Test.
Conclusion:
The advantage of Adhoc testing is to check for the completeness of testing and find more defects then planned testing. The defect catching test cases are added as additional test cases to the planned test cases.
Adhoc Testing saves lot of time as it doesn't require elaborate test planning, documentation and test case design.
Adhoc testing: testing type, considered to be part of exploratory testing. It performed without planning, without documentations, and it is intended to be run only once , unless a defect is discovered
