Ad-hoc Testing | Manual Testing Tutorial PDF

Ad-hoc Testing: -

In general, every testing team conducts planned testing, but testing team adopts informal testing sometimes due to some challenges or risks.
Eg: Lack of time, lack of resources, lack of team size, lack of skill, etc.
This informal testing is also known as Ad-hoc testing. 

There are different styles in Ad-hoc testing.
a) Monkey Testing
b) Buddy Testing
c) Exploratory Testing
d) Pair Testing
e) Defect Seeding / Debugging

a) Monkey Testing: -

Due to lack of time, the testing team concentrates on some of the main activities in the software build for testing. This style of testing is known as “Monkey testing” or “Chimpanzee testing” or “Gorilla testing”.

b) Buddy Testing: -

Due to lack of time, the management groups programmers & testers as “Buddies”. Every buddy group consists of programmers & testers.
Eg: 1:1 (or) 2:1 (or) 3:1 (preferable)

c) Exploratory Testing: -

Due to lack of proper documentation of the software being built, the test engineers depend on past experience, discuss with others, browse the Internet or Operate similar projects and contact customer side people if possible.
This style of testing is called “Exploratory Testing”.

d) Pair Testing: -

Due to lack of knowledge on project domain the management groups a senior tester & a Junior Programmers are developed and conducted testing, these all are called Pair testing.

e) Defect Sending: -

To estimate the efficiency of test engineers, the programmers add some bugs to the build. This task is called defect seeding / debugging.