Exploratory Testing

We have to explore the application, understand completely and test it.

Understand the application, identify all possible scenarios, document it then use it for testing

We do exploratory testing when the application is ready but there is not requirement.

Drawback:

You might misunderstand any features as a bug or any bug as a features since you do not have any requirements

Time consuming

if there is any bug in application, you don't know about it.

Adhoc Testing

Testing application randomly without any test cases or any business requirement document.

Adhoc Testing is an informal testing type with an aim to break the system

Tester should have knowledge of application even though he doesn't have requirements/ test cases.

This testing is usually an unplanned activity.

Note:

No document

No test design

No test case

Monkey/ Gorilla Testing

Testing application randomly without any test cases or any business requirement document

Adhoc testing is an informal testing type with an aim to break the system

Tester do not have knowledge of application

Suitable for gaming applications

Adhoc Testing Vs Monkey Testing Vs Exploratory Testing

No document No document No document

No plan No plan No plan

Informal testing Informal testing Informal testing

Tester should know application functionality Tester doesn't know application functionality Tester doesn't know application functionality

Random testing Random testing Random testing

Intension to break app, and find defects Intention to break app and find out defects Intension to learn or explore functionality of app

Any applications Gaming applications Any application which is new to tester