Delivered by FeedBurner

Exploratory testing is basically Black Box testing, we do not need to worry about internal coding of the software while performing the Exploratory Testing. In simple word Exploratory Testing is all about simultaneously Learning, Test Design and Test Execution. Means here tester first learn about the software then write the test cases  or test scenario for it and then execution of those written scenarios all this at on the fly. And this learning about the software needs not to be in sequence. Means tester may choose any feature any module and start learning about it. Tester has the freedom to do whatever he wants; this testing totally depends on the tester creativity, thinking and domain knowledge of the Tester.

Why do we calls exploratory testing is depends on tester creativity and thinking? so if you have these question in your mind then the answer is , in Exploratory testing we do not write test cases in advance here tester learn about the features and about the module , write the test cases for it. So it totally depends on how much skilled and quick learner tester are. Where as in other type of testing they write the test cases in advance then they just execute it on the software which is we can called it non – thinking activity just need to follow the steps written in the test cases.

Module Controller in apache jmeter is one of the important and frequently used logic controller in any software web applications load test plan. Earlier we learnt usage of different jmeter logic controllers with example which are listed on Jmeter Tutorial but module controller is different from all of them. Module controller allows you to redirect test execution to a given fragment of the test or you can say selected module. Let's take simple example to understand usage of module controller better for your software web application's load testing.

Adhoc testing is one of the widely used testing practiced, this is informal type of testing where any kind of documents are not prepared. And testing is done without creating the test cases. The main aim of this testing is to find bug by testing the functionality randomly and providing random inputs.

When to perform or when Adhoc Testing is preferred: there are many occasion when this AdHoc testing is preferred. One of the occasion is when there is less time remaining for the testing team to test then AdHoc Testing is preferred. Another occasion is when there is less software specification document are available then also AdHoc testing is preferred. This testing also performed when formal testing is done. To before the release this testing is also done to ensure that system is working properly.

Points to Remember : When to perform AdHoc Testing:
  • when there is less time.
  • when less software specification document available.
  •  performs after formal testing or perform before release.