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

The exploratory concept of software testing training has been put forward for some time. Do you know this concept? At present, there is a department of learning and research in China, but it has not really been put into use. Today, the editor will popularize the knowledge about this aspect for everyone!

Many people still feel confused and confused after reading some books, and doubt whether there is something wrong with their abilities. I felt the same way at first. I felt that after reading the definition and explanation of some experts, I still didn't understand what exploratory testing is. Having seen an example of a game, I suddenly became enlightened. Suddenly there was an idea that "the previous explanation is not that we can't understand it, but that the definition itself is not clear, or that some translations are too blunt." Everyone should have their own opinion on whether exploratory testing is good or not; how to use exploratory testing, each team should also judge according to their own actual situation; but generally speaking, I think, at least there are many good methods in exploratory testing, and good testing ideas are worth learning. Good things, no matter which faction they belong to, can be integrated as long as they have mastered them, thus greatly increasing our skills.

First of all, let me give you an example to understand what exploratory testing is. For example, we have bought a new robot toy, but we still don't know how to control it or how to use it. Usually we will read the instruction manual first, and then we can't wait to operate it. At this time, we need to study the instructions while actually operating how to use and observe the results of the use. If we use it incorrectly, we will continue to study and think until we understand the basic usage and learn to use it. This process of learning and using is the process of our exploration; in fact, this process is similar to the process of exploratory testing.

What exactly is exploratory testing?

Exploratory testing (Exploratory Testing)

I think it is a type of test first, and then it is tested in an exploratory way.

"Exploration" shows that the software is still unknown, need to study, to learn, to explore.

There is no standard method or technology for exploratory testing. As long as we have good experience, good ideas and good methods, we can use it to explore.

Like the exploratory testing model summarized by James Whittaker, we can be used as the basic model of exploratory testing, but the methods and ideas of exploratory testing are not limited to this. We must not do two things: "all foreign experts are right, and all foreign experts are the standard." Even James Whittaker himself has said

We can summarize our own exploratory testing methods through practical experience.

In short, I think exploratory testing is the use of new testing ideas, while learning, design, testing, thinking.

What is the purpose of exploratory testing?

Exploratory testing applies to a number of scenarios or purposes (here are just some of them):

You need to learn a product quickly.

Need to seek a variety of tests

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

Want to find the most serious bug in the shortest time

Want to check the work of a tester

But I think the purpose of exploratory testing is to clean up defects.

Through new ideas, new methods, to find the problems that have not been discovered, to sweep away the fish that have missed the net.

Conditions of exploratory testing

Project requirements:

Product stability

Products are important

Tester requirements:

Passionate and interested

Master the theory and method of exploratory testing

Under what circumstances do you use exploratory testing?

In our daily testing, we usually carry out 2-3 rounds of testing. in our country, we generally write test cases according to the requirements, in which different test case design methods are considered. But when the same use case is executed for the last time, it is basically difficult to find the problem. At this time, if we can change the test idea and add some new test points, maybe we will find a new bug.

So I think it would be more appropriate to put the exploratory test in the third round. Maybe some people will say that exploratory testing is suitable for every stage; I think good testing ideas and testing methods can be used at any time, but the use of exploratory testing in the system, I think it is more appropriate to put it in the last few stages.

How to conduct exploratory testing?

The steps given in the exploratory testing practice:

Step 1: look at the various documentation available, such as PRD and prototypes.

Step 2: determine the core functional modules.

Step 3: communicate with the testers of the project team to determine the module with the most risk of bug.

Step 4: make an exploratory plan: the number of ranges, the tasks of each range, and the time of each range.

Step 5: execute according to the plan:

Step 6: according to the plan, learn, design, test and think; modify the test strategy at any time according to the specific situation.

Part VII: sending defect reports.

In fact, whether the fourth part should be carried out or not, I think it can be done in the light of the actual situation.

The steps I have summarized are:

1. Read the requirements document and determine the core module.

2. Check the bug management system or communicate with the testers to determine the modules with more problems.

3. According to the demand, explore the function of the core module.

4. According to the heuristic test strategy model and roaming test model, the supplementary test strategy is selected for testing.

5. According to the plan, we should study, design, test and think about it, and modify the testing strategy at any time according to the specific situation.

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.