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

1. Software testing purpose

(1) testing is the process of executing a program in order to find errors in the program.

(2) A good test scheme is one that is very likely to find errors that have not been found so far.

(3) A successful test that finds errors that have not been found so far.

two。 Software testing criteria

(1) all tests are traced back to user requirements.

(2) A test plan should be made long before the test begins. In fact, once the requirements module is completed, you can start to develop the test work, and you can start to design the detailed test plan as soon as the design model is established. Therefore, all testing work can be planned and designed before coding.

(3) apply Pareto principle to software testing. The Pareto principle states that 80% of the errors found by tests are likely to be caused by 20% of the modules in the program.

(4) We should start with "small-scale" testing and gradually carry out "large-scale" testing. First, focus on testing a single program module, and then the focus of the test turns to looking for errors in the integration module cluster, and finally looking for errors in the whole system.

(5) exhaustive testing is possible. Tests can only prove that there are errors in the program, not that there are no errors in the program. However, if the test scheme is carefully designed, it is possible to fully cover the program logic and make the program achieve the required reliability.

(6) in order to achieve the best test results, the testing work should be carried out by an independent third party.

3. Testing method

First, black box testing, also known as functional testing, knows the functions that the product should have, and verifies whether each function of the product is in normal use through the test. Second, the white-box test is the structure test, which is used to verify whether the internal action of the product runs normally in accordance with the provisions of the planning manual.

4. Test procedure

(1) Module testing

In a well-designed software system, each module completes a clearly defined sub-function, but there is no interdependence between this sub-function and the functions of other modules at the same level. The purpose of module testing is to ensure that each module can run correctly as a unit, so module testing is also called unit testing. This test often finds errors in coding and detailed design.

(2) Subsystem testing

The modules of the unit test are put together to form a subsystem for testing. The coordination and communication between modules is the main problem of this test module, so this module focuses on testing the interface of the module.

(3) system testing

Not only send design and coding errors, but also verify that the system can indeed provide the functions specified in the specification, and the dynamic nature of the system also meets the requirements.

(4) acceptance test

The software system is tested as a single system, and the testing content is basically the same as the system testing, but it is carried out with the active participation of users.

(5) platform operation

Run both the newly developed system and the old system it replaced in order to compare the processing results of the two systems. Objective: 1. Can run the new system in a quasi-production environment without risk; 2. Users can have a period of time to be familiar with the new system; 3. Can verify documents such as user guides and user manuals; 4. The new system can be fully tested in quasi-production mode, and the test structure can be used as the verification performance index.

5. Test phase information flow

Two categories, first, software configuration, including requirements specification, design specification source program list; second, test configuration, including test plan and test plan.

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.