(Software Engineering video summary) test

After each software development, there will inevitably be errors and defects, so before putting into use, we have to test the software. The purpose of software testing is to discover errors in the software. A good test case is to find errors that have not been discovered so far, and a successful test is a test that finds errors that have not been discovered so far. Testing is not just the right test procedure, but also a test of the document.

The principle of software testing: 1. The test case should consist of the test input data and the corresponding expected output result two parts. 2. Programmers should avoid checking their own programs. 3, in the design of test cases, should include reasonable input conditions and unreasonable input conditions.

Two commonly used test methods: black-box test and white-box test.

Black box test the main test function, so called functional testing or data-driven, mainly check the interface between the modules, check the function and performance of the unit under test. Some of the exhaustive tests are impossible to complete.

Black box testing is divided into: Equivalence class division, boundary value analysis, error inference method, causality diagram

White box test mainly test structure, so called structural test. All independent (primary) paths in the module are tested at least once. All logical conditions are tested once when they are set up or not.

White box testing is divided into: statement coverage, decision coverage, conditional coverage, decision-conditional coverage, conditional combination coverage, path coverage.

Test process: Unit test, assembly test, validation test and system test

Types of tests: functional, reliability, strength, performance, recovery, start/stop, configuration, safety, usability, support, installation, process, interconnect, capacity, and document testing, test and test

The program is debugged after the test. Debugging steps: 1, from the wrong external manifestations, to determine the location of the program error. 2, study the relevant part of the procedure, find out the internal causes of the error. 3, modify the design code to exclude this error. 4. Repeated exposure to the original test of this error or some relevant tests.

Debugging methods: Forced error, backtracking debugging, inductive method, deduction

Principles of Commissioning: 1. Use the mind to analyze the information related to the false indications. 2, avoid dead end. 3. Only use debugging tools as auxiliary means. 4, avoid the use of heuristics, at most can be regarded as a last resort.

When we modify the error, it is not only in the wrong place to modify it, in general, there will be errors around the error. Also, we should be careful when modifying errors by not modifying old errors and introducing new ones.

Don't forget to write a test analysis report after the test. This facilitates the developer to make the modification, also facilitates the management personnel to the software better understanding.

Software testing tells us that we develop the software will have a hidden error, we should try to test out as far as possible, fix the error, to ensure that the user's normal use. Moreover, we should standardize their own coding and other development behavior, so as to play the role of the team!

(Software Engineering video summary) test