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. 

Types of Adhoc Testing

Adhoc testing is divided into three types as follows. 

1. Buddy Testing - Buddy testing is a type of Adhoc testing where two bodies will be involved one is from the Developer team and one from the tester team. So that after completing one module and after completing Unit testing the tester can test by giving random inputs and the developer can fix the issues too early based on the currently designed test cases. 
   
2. Pair Testing - Pair testing is a type of Adhoc testing where two bodies from the testing team can be involved to test the same module. When one tester can perform the random test another tester can maintain the record of findings. So when two testers get paired they exchange their ideas, opinions, and knowledge so good testing is performed on the module. 
   
3. Monkey Testing - Monkey testing is a type of Adhoc testing in which the system is tested based on random inputs without any test cases the behavior of the system is tracked and all the functionalities of the system are working or not is monitored. As the randomness approach is followed there is no constraint on inputs so it is called Monkey testing.

Characteristics of Adhoc Testing

• Adhoc testing is performed randomly. 
• Based on no documentation, no test cases, and no test designs. 
• It is done after formal testing. 
• It follows an unstructured way of testing. 
• It takes comparatively less time than other testing techniques. 
• It is good for finding bugs and inconsistencies that are mentioned in test cases.

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.

When not to conduct Adhoc testing

• When an error exists in the test cases. 
• When Beta testing is being carried out.

Advantages of Adhoc testing

• The errors that can not be identified with written test cases can be identified by Adhoc testing. 
• It can be performed within a very limited time. 
• Helps to create unique test cases. 
• This test helps to build a strong product that is less prone to future problems. 
• This testing can be performed at any time during Softthe ware Development Life Cycle Process (SDLC)

Disadvantages of Adhoc testing

• Sometimes resolving errors based on identified issues is difficult as no written test cases and documents are there.  
• Needs good knowledge of the product as well as testing concepts to perfectly identify the issues in any model. 
• It does not provide any assurance that the error will be identified. 
• Finding one error may take some uncertain period.

Five practices to follow to conduct Adhoc testing

1. Good Software Knowledge. 
2. Find Out Error-Prone Areas.  
3. Prioritize Test Areas. 
4. Roughly Plan The Test Plan. 
5. Use of the right kind of tools.