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

The core of software testing is test design, and the quality of test design largely depends on whether the tester's thinking is open and in place. Here are some of my testing ideas for the vss2 project to discuss with you:

The entire test plan is divided into the following four parts:

1. Write a test plan based on the test cycle (20%)

two。 Write test cases (30%)

3. Actual testing (module testing, integration testing, stress testing) (25%)

4.Bug tracking (25%)

At the same time, in the process of product design, some suggestions are put forward from the point of view of customers and QA, such as:

Is this a "real" demand?

Is the demand complete?

Are the requirements compatible?

Is the requirement achievable?

Is the demand reasonable?

Is the requirement measurable?

Strive to do less repetitive work, and the coverage of test cases is as wide as possible.

Mode of thinking

1. Reverse way of thinking

According to the result, the equivalent class division of the input condition is obtained, and the loophole in the developer's thinking is found.

2. Combinatorial thinking mode

Arranging (ordered) and combining related things (out of order) makes the complexity of the program to a higher level and increases the defect rate of the program.

3. Global way of thinking

Analyze the system to be tested from multiple angles; try to look at the system in different roles and analyze whether it can meet the requirements.

4. Bipolar mode of thinking

In extreme cases, see if there are defects, such as boundary value analysis.

5. Simple way of thinking

According to the nature of the problem, eliminate the interference factors, so that the cause of the problem is exposed.

6. Comparative mode of thinking

Find out the problem by comparing the normal situation with the abnormal situation.

Testing in the design phase:

By examining the design documentation, how the system will work if the development is carried out according to the design. To make a test plan.

Supervise R & D to conduct white-box testing, including:

Key test

Internal boundary test

Specific algorithm testing

Structural testing and functional testing

Growth test and crash test

Black box test

Two test cycles:

All defects are found in the first cycle, and the effect of the change is verified in the next cycle. It is likely to take eight cycles. If each version is not thoroughly tested, 20 or 30 (or more) cycles should be expected.

Black box test event sequence

Design test plans and test cases.

Design of a single test

A comprehensive test plan

1. Test plan

two。 Acceptance test

When you receive a new version, first check whether it is stable and can be tested. If it crashes in a very small test, it shows that this version does not meet the test requirements.

3. Initial stability assessment

4. Functional testing, system testing, acceptance and confirmation

5. Beta test

Use the product and submit suggestions on behalf of the market user group

6. Integrity testing and release testing

7. Final acceptance testing and certification

two。 Test case design

Write test cases with the mentality of trying to overturn it, and strive to move closer to the following:

There is a good chance of finding software errors.

It is not redundant

The best in this class of use cases

Neither too complicated nor too simple

Is this a "real" demand?

Is the demand complete?

Are the requirements compatible?

Is the requirement achievable?

Is the demand reasonable?

Is the requirement measurable?

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.