In general, every testing team conducts planned testing, but testing team adopts informal testing sometimes due to some challenges or risks.
E.g : Lack of time, lack of resources, lack of team size, lack of skill, etc.
There are different ways of Ad-hoc testing.
Ways of Adhoc Testing
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”.
Buddy Testing
Due to lack of time, the management groups programmers & testers as “Buddies”. Every buddy group consists of programmers & testers.
E.g.: 1:1 (or) 2:1 (or) 3:1 (preferable)
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”.
Pair Testing
Due to lack of knowledge on project domain the management groups a senior tester & a Junior Programmers and conducted testing, these all are called Pair testing.
Defect Seeding
To estimate the efficiency of test engineers, the programmers add some bugs to the build. This task is called defect seeding / debugging.
