[Mention] defect analysis test code requirements and design documents did not match

1. Demand Background

Design a service, you can query the database according to upstream service incoming data, database design is divided into three tables, version control table, table resource path, resource allocation table, requires business people can be configured to trigger service resources through version control table configuration database associated path tables and resource allocation table data query, and returns the score associated with the query

2. Description defects

Service staffing a field data table resource configuration 0.00002, request test data server interface discovery an error log server, Throws

Expected: the ability to get normal access and query interfaces score returned

3. Discovery Process

3.1 When a defect is discovered

After the function test, pressure test preparation stage before the on-line discovery

3.2 Why a defect is discovered at this stage

This stage of the import 600,000 actual business scene data, comprehensive coverage scenarios

3.3 should find defects when

You should find the defect in the function test parameters checking module

4. scope

Traffic entering the range of the configuration are not available

5. Analysis

1. Development code design not in accordance with requirements and design documents, the field range requirements and design documentation requirements of resource allocation table (0,100), but the development in the design of the code determination (0.0001,100), so the service personnel this field configured value is 0.00002, all associated with this configuration are invalid;

2. test cases, the boundary value method based module design described, with reference to the requirements and design documentation, the lower boundary value is "0", and therefore useful in Example Value: -1,0,0.1,0.55,1 (lower values ​​near the boundary), etc., that uncovered is greater than 0 is smaller than 0.00002 0.0001 (since the design does not match with the document, the omission case);

3. The total amount of operational personnel when importing data to enhance the use of the code coverage, so the defect is exposed

6. mitigation plans

1. Strengthen the specification requirements documentation and design documentation, material wealth, high demand everywhere should be treated;

2. Visual necessary to take comparative document design checking code (defined in the test, the test parameter ranges, etc.);

3. Strengthening of standard codereview requirements;

Scene is necessary to introduce the whole amount of imported data validation and acceptance testing on the front line 4;

The refinement of the test type

7. With the extension

1. Interface Design Parameter relevant range;

2. correlation algorithm logic threshold;

3. Other functional areas in need of parameter values ​​fixed range,

And so on, are likely to have this issue.

Guess you like

Origin www.cnblogs.com/flowertester/p/11603362.html