Ad-hoc Testing

Ad –hoc testing, also known as Random or Monkey Testing, is done without any planned testcases at
hand and the aim is to break the system without following any strict steps.

Usually, it is done before the Acceptance Testing and the defects found during the process are not easy to reproduce as there are no written steps. However sometimes the testers are able to find interesting defects which otherwise would be difficult to trace out. The success of the process depends on the creativity and curiosity of the tester.

How Ad-hoc Testing is useful for an under-development Product

One cannot override the importance of Ad-hoc Testing; the tester tries to find bugs by any appropriate means. Though, the planned testing has its own weightage but ad-hoc testing gives a complete sense of confidence before the release of the product.

Testing is a complicated process, some scenarios are best open-up while working directly on the product, and that’s where in the role of Ad-hoc testing kicks in.

Sanity Testing

Once a new build is provided to the QA team with bug fixes or functionality enhancement, a small testing is done just to check that the targeted paths are working fine. This process is known as Sanity testing. This is a narrow and deep process where only a subset of testcases is run to make sure that new build is stable.

The aim of this testing is to minimize the time wastage if the build is not stable. The QA team can immediately reject the new build upon the failure instead of completing all the runs. We can also term Sanity testing as a subset of Regression testing.

Follow us onFacebooktwitterlinkedininstagram
Share the postFacebooktwitterlinkedin
Quick Connect