Tests as Experiments....Exploratory Testing

Today I am writing about exploratory testing...This is randomly testing technique sometimes we will get the issue or bugs which we are not expected while acceptance testing. This testing will be done by anybody in an organization .it is a very simple and plane like ad-hoc no rules no test case.ex: keyboard banging involved in Exploratory. Randomly press any key or in an any sequence. There can be any number of unintended consequences that acceptance tests would not expose.

Note that each of our experiments involves a hypothesis a prediction about the resulting behavior of the system. We might start with a hypothesis that the system will be able to handle what we are throwing at it.

When we design tests while exploring, we have a hypothesis about how the software will behave. While the software is being tested, the tester learns things that together with experience and creativity generates new good tests to run. His comes under black box testing technique. It can be done by the Jr tester as well.

Exploratory testing is particularly suitable if requirements and specifications are incomplete, or if there is lack of time. And experienced tester easily get the defects.

How do u know when u have to stop testing.
when we have no more charters left under given story?
When we find no new interesting information.
When additional information would not help move the project forward.