Shulou(Shulou.com)06/03 Report--

"any sufficiently advanced technology looks like magic," said Arthur Clark, a famous British futurist who published the classic science fiction novel Sky Odyssey 2001.

Exploratory testing (Exploratory Testing, also known as exploratory testing) is a software testing method, which was first proposed by Cem Kaner in 1983. This is a testing method that emphasizes individual freedom and responsibility, so that independent testers can use continuous learning to improve test planning and test execution, and at the same time improve test cases to complement each other in the testing process. This novel, interesting and creative testing method has been used in many projects of Nortel and Microsoft. James Whittaker, a practitioner of exploratory software testing and a master of software testing, makes a comprehensive interpretation and innovation of this method in his new book exploratory Software testing, showing the experience of using this method within Microsoft.

This method has been put forward a long time ago, and many people in our country have begun to study and study it, but it is rarely used in enterprises. Recently, it has been found that this method has been gradually accepted by people. Whether you go to a sharing meeting or a salon, it is involved, so let's learn about it.

According to du Niang: exploratory testing can be said to be a kind of testing thinking technology. It does not have many practical testing methods, techniques and tools, but it is a way of thinking that all testers should master. It exploratively emphasizes the tester's subjective initiative, abandons the complicated test plan and test case design process, and emphasizes changing the test strategy in time when there is a problem.

Top test believes that exploratory testing is the use of new testing ideas, while learning, design, testing, thinking.

I. the basic process of exploratory testing

a. The purpose of exploratory testing and identification software system

b. Identify the functions provided by the software system

c. Identify potentially unstable areas of the software system

d. Record information and questions about the software in the process of exploring the software system

II. Exploratory software testing types

a. Free exploratory test

b. Scene-based exploratory testing

c. Policy-based exploratory testing

d. Exploratory testing based on feedback

Third, the purpose of exploratory testing

a. You need to learn a product quickly.

b. Need to seek a variety of tests

c. After script testing, you want to do a variety of tests.

d. Want to find the most serious bug in the shortest time

e. Want to check the work of a tester

IV. Conditions for exploratory testing

a. Project requirements

b. Product stability

c. Products are important

d. Tester requirements

e. Passionate and interested

f. Master the theory and method of exploratory testing

5. Use exploratory testing for what or what time

After we have passed several rounds of software testing, the basic functions are relatively stable. When we write Test Case (test cases) according to Test Requirement (test requirements), some problems that are difficult to find will inevitably occur in the process. Testers need to change relevant ideas and add more test details.

6. How to conduct exploratory testing

a. Look at PRD (Product requirements document, product requirements documentation) and prototypes and other available documentation

b. Identify core functional modules

c. Communicate with the testers of the project team to determine the module with the most risk in bug

d. Develop an exploratory plan: the number of distances, the tasks of each range, and the time of each range

e. Execute according to the plan

f. According to the plan, learn, design, test and think; modify the testing strategy at any time according to the specific situation

g. Send defect report

Summary of test results

a. Read the requirements document and determine the core module

b. Check the bug management system or communicate with testers to identify modules with more problems

c. Explore the functions of the core module according to the requirements

d. Select supplementary testing strategies for testing according to heuristic test strategy model and roaming test model

e. According to the plan, learn, design, test and think; modify the testing strategy at any time according to the specific situation

VIII. Existing misunderstandings

Myth 1: exploratory testing is a testing technique.

Exploratory testing, as a method, can be applied to any use case testing, such as unit testing, functional testing, performance testing, system testing and so on. Exploratory testing will play an important role in finding dangerous areas that are not covered by use case testing.

Myth 2: exploratory testing is a black box test.

One of the principles advocated by exploratory testing is "strive to gain an in-depth understanding of the product under test". With more and more in-depth understanding of the product, exploratory testing will gradually discover more hidden potential risks, and exploratory testing in the white box state is usually more valuable, because the results are based on solid knowledge and understanding, and its direction is more targeted.

Myth 3: exploratory testing is random testing.

Exploratory tests have written records and do coverage analysis, which is more orderly and controllable than random tests.

Myth 4: the exploratory testing phase is after use case testing.

Exploratory testing is applied to all stages of testing to maximize its value as much as possible.

Myth 5: exploratory testing requires a veteran.

Agile testing expert Lisa Crispin summarizes the necessary skills:

Careful observer: observe abnormal and unexpected results, be careful with correct assumptions, and be able to observe software features or patterns in detail.

Serious thinker: checking the test in the run and changing it in an unexpected direction can explain the logic of finding defects and provide a clear test status.

The rebel of the system: rigorous thinking, systematization, but also a variety of viewpoints.

Resource diggers: exploration testers should explore more tools, techniques, test data, friends, and sources of information that they can use.

The application of exploratory testing in the game is also instructive. Using exploratory tests several times in a row can familiarize the testing thinking of your corresponding methods; the methods found in the same way of thinking are easy to learn when testing similar functions.

In a recent test salon, a teacher put it this way: ST is equivalent to a group tour, and ET is equivalent to jungle exploration.

Through the collation of the data, I believe everyone is relatively clear.

Smpidus made a personal comment:

1. Beginners with weak learning ability can not achieve the desired results in the first place, but because of their simple thinking, we can see the essence more clearly. (alas, he is clearly talking about me. I am of this kind.)

two。 Beginners with strong learning ability can explore better through new things.

3. Experienced veterans will refine and perfect the original things.

To measure whether a person is fit to use ST is explored by our skills, not by a novice or a veteran. In the product is relatively stable, further supplement, covering the system test can not be the scene.

Since we are engaged in a certain industry, there is no question of whether it is suitable or not, but from what point of view we should consider the problem. The arrangement is not perfect. I hope you can put forward your shortcomings and your own point of view.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.