Four types of exploratory software tests-testing methodology

The four types of exploratory software testing, exploratory testing are divided into free-type exploratory test, scenario-based exploratory testing, policy-based exploratory testing and exploratory testing based on feedback. The following 4 types of scenarios are described in detail.

One: free-type exploratory testing

Freestyle exploratory testing refers to all the functionality of an application, randomly probing in any order, using any amount, regardless of which features must be included. Freestyle testing doesn't have any rules or patterns, just keep doing it. Unfortunately, many people think that all exploratory tests are free, and in the long run, this perception is muttering about the ability to explore test techniques, and we will see some variants of such tests later on.

A free test case may be selected as a quick smoke test to check whether a major crash or serious software flaw is found, or to familiarize yourself with an application before adopting advanced technology. Obviously, free exploratory testing does not have to be a lot of preparation rules. In fact, it's more like "explore" than "test", so we should adjust our expectations accordingly.

Free-type testing does not require much experience or information. However, combined with the exploratory techniques mentioned below, it will become a very powerful test tool.

Two: scenario-based exploratory testing

Scenario-based exploratory testing is similar to traditional scenario based testing. Both involve an open store, a user story, or the beginning of a documented end-to-end scenario, where we expect end users to start executing applications. These scenarios can come from user research, applications, previous versions of data, and so on, and are used as scripts for testing software. Exploratory testing complements traditional scenario testing the scope of the script is extended to change, investigate, and change the user execution path.

Exploratory testers who use the scenario as a guide often modify the input that he dares to be interested in or pursue some potential side effects that are not included in the script. However, since the final table does not complete the given scenario, the detours on these tests will always go back to the main execution path of the user in the script file record.

Three: policy-based Exploratory testing

Merging the free-type test Explorer with the experience, skills, and perceptions of the Test veteran becomes a policy-based exploratory test. It belongs to the exploration of the free type, but he is guided by the existing error search technology. Policy-based Exploratory testing uses all known technologies (such as boundary value analysis or combinatorial testing) and unknown instincts (such as exception handling that are often prone to software defects) to guide testers to test.

These known strategies are key to the success of policy-based exploratory testing, and the richer the knowledge of the tests, the more efficient the tests are. These strategies are due to accumulated knowledge, they guide software defects hidden where, how to synthesize the human input data, those code path often fail.

Policy-based Exploratory testing combines the experience of the Test veteran and the randomness of the exploratory tester.

IV: Exploratory testing based on feedback

The exploratory test based on feedback is due to the free test, but as the Test history is formed, testers will use feedback to guide future exploration. "Overlay" is a typical example. A tester selects new test cases by consulting those coverage metrics (code overlay, user interface overlay, feature overlay, input overlay, or some combination of them) to improve these coverage metrics. The coverage index is only one of the signs that contains feedback information. We will also look at other signs, such as the number of code changes and software defect density.

A "last Test" of exploratory testing based on feedback: The last time I selected an input based on the last state of the application, the next time I selected another input. Or, I used the A attribute the last time I encountered this interface, and this time I used the B attribute.

The exploratory testing tool based on feedback is very valuable, it can be the tester to save, search the history of the test and take action in real time accordingly. Unfortunately, such tools are rare.

Original from: Http://www.ltesting.net