Ad-hoc testing is an integral part of software testing that can be proven beneficial in different situations. So in this chapter, you'll learn about another kind of software testing.
Ad-hoc testing can be defined as an informal type of testing having a focus on breaking the project or application into sub-parts. Ad-hoc testing can be considered typically as an unintended action of testing and doesn't track or follow any design method for testing for creating test-cases.
Ad-hoc Testing doesn't follow the organized way to test an application and hence randomly actions are done on different parts of the project. This testing aims at finding defects randomly by checking anywhere and at any moment. This can be accomplished through Error Guessing technique of testing. Many people can experience this type of tests on the product for "guessing" bugs or errors if he knows where he or she needs to check.
Different Forms of Ad-hoc Testing
- Buddy Testing: This is named from the concept that, if two buddies or friends where one is from the development team and other is from the test team jointly work to identify defects in the project, you can call it a type of ad hoc testing. This type of testing benefits the testers in developing finer test cases, and hence the development team can make changes to remove bug at early stages. This testing type is performed after completion of unit testing.
- Pair Testing: In this case for a single module 2 testers are given the same task, and they share their ideology for finding defects; where one is responsible for executing the tests while another person for recording the notes as what they found and document it.
- Monkey Testing: In this type of testing, tests are being performed haphazardly or randomly for breaking into the system to found a bug. This type of testing is being done mainly by licensed penetration testers.