Beijing Btestsky is a national evaluation laboratory, with CNAS evaluation qualifications, specialized in software acceptance testing, and can be given an authoritative third-party test report; With more than 10 years of experience in software evaluation, a complete set of complete and professional test procedures and methods are developed in the acceptance test field. Let us introduce the system function test below.
The system function test is performed after the integration test is completed, and is tested for the application system. The function test is based on the product function specification and the user angle to verify all functions to confirm whether each function can be used normally.
Function test flow chart.
1.Test target.
2.Demand review.
3.Test plan & system test
4.Use case design
5.Design review.
6.The design of the functional test.
7.Code review.
8.Function test.
9.System test.
10.Acceptance test.
The purpose of functional testing is to determine whether the function of the actual software meets the user's needs.
The content of the function test:
1. Normal function.
(1) to detect whether the normal conditions of each module can be executed correctly;
(2) to detect the normal operation of the system and whether the normal process can be executed properly;
(3) the coordinated operation of each subsystem associated with the normal condition.
2.Abnormal function, including but not limited to the following situation: database server crash, data table damage, network failure, software server failure, etc.
(1) the abnormal situation of the detection module can be executed correctly;
(2) the abnormal operation of the detection system and the fault-tolerant treatment can be executed correctly;
(3) the detection of each subsystem associated with the abnormal condition can coordinate the operation and can form a closed-loop.
3.The boundary test.
Test when input or output is the maximum, minimum, critical value of the module or system can be handled correctly.
4.The interface test.
(1) check whether the interface style conforms to the system development specification;
(2) check whether the interface can support the disorder of the operating order;
(3) check whether the interface is convenient and whether there is a shortcut, whether there is an online help.
5. Interface test.
Detection system and other soft, hardware system interface correctness.
6. Error handling test.
(1) to examine the effectiveness of the unqualified input and error data, the error operation, and the illegal sexual judgment;
(2) the description of the error hint is clear whether it is easy to make a wrong location.