Software Testing Concepts

Regression test (Regression testing): Run a test case that was previously used by the program to find errors after the software has been modified.

Unit testing: To detect and eliminate grammatical errors, logic errors, correct implementation errors, meet their needs, and test the module.

Integration Test (Integrated testing): Assemble the tested modules for inspection.

Acceptance Testing (Acceptance testing): A formal test to determine whether the software system meets the acceptance criteria and enables the customer to decide whether to accept them.
Errors in the program are not necessarily caused by coding, but may be due to detailed design, design, or even the problem of demand analysis. Problem solving, Correcting errors must also be traced back to the previous work. This is one of the reasons why the tests are divided into so many steps. Unit tests verify that each module works independently to identify the coding and algorithmic problems of the module. And then connect multiple modules together, Conduct integration testing to examine the problem of interface design for the module in the profile design. Validation tests should be based on the requirements of the specification as a test scale to identify the problem of demand analysis. The final system test is to synthesize the software and hardware and other related factors (such as personnel operation, data acquisition) into a comprehensive inspection. .

Smoke test (smoking test) Smoke testing is a predictive test of the software submitted for testing prior to detailed in-depth testing, the primary purpose of which is to expose serious problems such as the failure of basic functions that cause the software to be republished. Smoke tests can be performed by a developer or by a tester. That is, the developer executes the test before it is formally submitted after the build is compiled, or after the release is developed, the tester executes before accepting this version for further testing as a formal version. Microsoft has proposed that after reviewing the code for changes, the smoke test is the most cost-effective way to confirm the defects of the repair and the effectiveness of the functional changes. Smoke tests can be performed manually or automatically after version compilation, which is a confirmation of the basic functionality, non-in-depth testing, but covering to the polygon, i.e. all change points are confirmed. With automated execution, the daily smoking test can be combined with the daily component, and if the test passes, the changed code is automatically merged into the skeleton Code repository as the version of the formally submitted test.