Testing the application randomly without looking into the requirement and without proper planning and documentation is called as Ad hoc Testing. It is an informal testing type with an aim to break the software. It is usually conducted by the test engineer who has strong knowledge of the software.
In below mentioned video you can see how to do adhoc testing
Why we should do ad hoc testing?
1. Chances are there end users or customers might use the application randomly and they might find defects to avoid that we should do ad hoc testing.
2. Developer will develop software as per the requirement and test engineer will test the software as per the requirement chances of finding defect is less if you look in requirement and test the software so we should come up with creative scenarios and test the application by doing ad hoc testing.
3. Since it is a negative testing ad hoc testing should be done.
4. Since requirement are not followed ad hoc testing should be done.
5. The intention of doing ad hoc testing is to some how break the product.
How to do ad hoc testing?
To understand how to do ad hoc testing let's take an example of gmail web application.
Application: Gmail
Scenario 1: Login as user into gmail click on compose enter values for all the fields, click on send, click on logout, click on browser back button and check whether login page is displayed.
Scenario 2: Open the browser enter url for gmail login page will be displayed enter valid username and invalid password click on login error message should be displayed.
Scenario 3: Open browser enter url for gmail login page will be displayed enter valid username and password switch off internet connection click on login proper error message should be displayed.
Scenario 4: Login as user A click on compose copy the url logout from user A paste the url login page should be displayed.
When to do ad hoc testing?
1. As soon as we get build first we should do smoke testing since smoke is a positive testing here we should not do negative testing.
2. While doing functional testing, integration testing and system testing in between or at the end if you have some time we can do ad hoc testing if time is not there document the ad hoc scenario and communicate to test lead.
3. Once after the complete software is tested as per the requirements then we can do ad hoc testing.
4. Once after the software is tested for 10 to 15 cycles and if the product is stable then we can do ad hoc testing.
5. While doing functional testing, integration testing and system testing if you come up with good ad hoc scenarios we can do ad hoc testing but don't spend too much time in doing ad hoc testing immediately switch back to functional testing, integration testing and system testing.
Why we should no to ad hoc testing in the early stage itself ?
1. As a test engineer first we need to check software is testable or not.
2. Customer always use software in positive ways so we should not do ad hoc testing first.
3. In the beginning only if you spend more time in doing ad hoc testing later we might not get sufficient time to do positive testing.
What are the types of ad hoc testing?
1. Buddy Testing: Test engineer will sit with developer come up with new creative scenarios and test the software is called buddy testing.
2. Pair Testing: Test engineer sit with other test engineer come up with creative scenario and test the software this is called pair testing.
3. Monkey Testing: Test engineer will test the applications randomly like a monkey without applying any logic.
ConversionConversion EmoticonEmoticon