Software Test Case standards

Software TestingUse CasesStandardSoftware Testing

Test cases are classified. If there is no scientific classification case, it is not easy to maintain and read.

It is best to write according to the standard: interface test cases, path test cases,Function TestingUse Cases, fault tolerance capabilities,Performance TestingTest cases, user interface tests, and informationSecurity Testing,Stress TestingUse Cases,Reliability TestUse Cases and installation/anti-installation test cases.

Test Cases and softwareQualityThere is a ing between features.

Software quality features:

Functionality: a set of functions (can meet the explicit or implicitRequirement.

Suitability: whether the software can provide a set of functions and the suitability of these functions.

Accuracy: whether the result or effect is correct or consistent.

Interoperability: ability to interact with other specified parameters.

Compliance: Enable the software to comply with relevant regulations, standards, conventions, and prescribed software attributes.

Security: prevents unauthorized/accidental access to programs and data.

Reliability: the ability of the software to maintain its performance level within a specified period of time and conditions.

Maturity: The frequency of failures caused by software faults.

Fault Tolerance: maintains the required performance level when the software fails or violates the specified interface.

Recoverability: After a failure occurs, rebuild its performance level and restore the capacity of directly affected data to achieve the time and effort required for this purpose.

Ease of use: users' efforts to use the software and their evaluations.

Comprehensibility: the effort required by the user to understand the logical concept and its application scope.

Easy to learn: the amount of effort you need to learn software applications.

Efficiency: the relationship between the performance level of the software under specified conditions and the amount of resources used.

Time features: Response and processing time and throughput when the software executes its functions.

Resource features: Number of resources used and time of use when the software executes its functions.

Maintainability: the effort required to make specified changes.

Easy to analyze: for DiagnosisDefectsOr the cause of failure and efforts required to determine the part to be modified.

Easy to change: efforts required to modify, eliminate errors, or adapt to environmental changes.

Stability: The level of risk caused by the revision that is unpredictable.

Testability: efforts are made to confirm that the software has been modified.

Portability: the ability of software to switch from one environment to another.

Adaptability: The software can adapt to different prescribed environments without additional special actions.

Ease of installation: the effort required to install software in a specified environment.

Compliance: enables the software to comply with portability-related standards or agreed software attributes.

　

Article from the collar test software testing network http://www.ltesting.net/