Software testing on-line standard
I. PURPOSE of preparation
Define the starting and ending standards for software testing work.
Second, the software testing eligibility criteria
The above ratio is the ratio of errors to the total test module.
Third, the defect repair rate standard
1) A, B, c level error repair rate should reach 100%
2) D-level error repair rate should reach more than 96%
IV. Coverage Standards
Test demand execution coverage should reach 100% (business test cases are executed).
V. Level of error
Class A: Not fully meet the system requirements, basic functions are not fully implemented, or endanger personal safety. The system is not able to continue running because of a collapse or hang.
Includes the following kinds of errors:
- Illegal exit due to the death caused by the program
- Dead loop
- The database has a deadlock
- program interruption due to incorrect operation
- Functional error
- Connection error with Database
- function does not match
- Data Flow Error
- Data Flow Error
- Serious numerical calculation error
B-level: Seriously affects the implementation of system requirements or basic functions, and there is no correction (re-security or restart of the software is not a corrective method). Causing the system to be unstable, or destroying data, or producing erroneous results, or some of its functions cannot be performed, and is an unavoidable major problem in regular operations or in unconventional operations.
Includes the following kinds of errors:
- Program Interface Error
- The system can be executed, but the operation function cannot be performed
- Invalid use of certain items (options) in a small feature item (non-fatal to the system)
- Incomplete feature implementation, such as deleting without considering data Association
- The implementation of the function is not correct, such as in the system implementation of the interface, some acceptable input control after the click of no effect, the operation of the database is not implemented correctly
- Report format and print content errors (rows and columns are incomplete, data is not displayed in the corresponding column, etc. causing incorrect data display results)
- Minor numerical calculation error
- Interface error (detailed documentation)
C-level: seriously affects the implementation of system requirements or basic functions, but there is a reasonable remedy (restarting the software is not a correction). Problems with limited impact such as system performance or response time slowing down, resulting in incorrect intermediate results without affecting the end result.
Includes the following kinds of errors:
- Operator interface error (including column name definition, consistency in data window)
- Print content, formatting errors (affects the format or appearance of the report only, does not affect the error of the data display result)
- Simple input restrictions are not placed in the foreground for control
- The delete operation is not prompted
- Although correctness is not affected, system performance and response time are affected
- Unable to locate focus or incorrect positioning, affecting function implementation
- The display format is incorrect but the output is correct
- Add and delete function, in this interface can not be implemented, but in another interface may be supplemented by the implementation.
Class D: Makes the operator inconvenient or troublesome, but it does not affect the execution of functions or important functions. Interface spelling error or user use inconvenient and so on small problems or need to improve the problem
Includes the following kinds of errors:
- Interface not standard
- The description of the auxiliary description is unclear
- Input and output not specification
- Long-time operation not prompting user
- Hint window text does not use industry terminology
- There is no obvious distinguishing mark between the input area and the read-only area
- Required fields and non-mandatory fields should be distinguished
- Invalid scroll bar
- Keyboard support is not good, such as in the field can be entered in multiple lines, do not support carriage return line, or the same field, different interface support different shortcuts
- Interface can not be refreshed in a timely manner, affecting function implementation
- Cursor Jump setting is not good, mouse (cursor) positioning error
- Some of the suggested questions
- System Processing not optimized
Software testing on-line standard