Getting Started with software testing

First, the software testing understanding

1. Software testing is an effective means to improve the quality of software, but software quality is not only tested.

2. Good testers not only have to master a variety of testing techniques and tools, but also have rich programming skills and sensitivity to bugs.

3. Software testing should be planned early, allocating good time, manpower, financial resources and so on.

4. Software testing is a batch of test cases carefully prepared according to the specification of the software development stages and the internal structure of the program, and uses these test cases to execute the program and discover the process of the program error.

Second, the software test object

1. Software testing runs through the entire period of software definition and development. Requirements analysis, summary design, detailed design, and program coding at all stages of the resulting documentation and source programs are software testing objects.

III. Types of software testing

1. Black box test: based on software requirements.

2. White box test: Based on the internal structure of the software.

3. Unit Test: The source code of the main test software module.

4. Integration testing: Integrate some "artifacts" together to test for proper operation. This "artifact" can be a program module, a client-server program waiting.

5. Functional testing: Test software functions to meet functional requirements, usually using black box test method.

6. System test: Test whether the software meets the requirements, including functional and non-functional, usually using black box test method.

7. Regression test: The re-test of the error is corrected or the software function, the environment changes. The difficulty is not determining what should be re-tested.

8. Acceptance test: Executed by customer or end user, test software complies with test specification.

9. There are also load tests, stress tests, performance tests, usability tests, installation and anti-installation tests, safety tests, compatibility tests, alpha tests, beta tests, and more.

Iv. Basic process of software testing

1. Develop a test plan.

2. Develop test cases.

3. Perform the test.

4. Write the test report.

5. Eliminate software defects.

V. Common sense and experience of software testing

1. Testing can improve the quality of software, but the improvement of software quality can not rely on testing.

2. The test can only prove that the defect exists and cannot prove that the defect does not exist.

3.80-20 principle: 80% of the defects are clustered in the 20% module.

4. Testing should be gradual.

Getting Started with software testing