Knowledge point 1: What is a smoke test? What is the purpose of the smoke test
1. What is a smoke test?
Smoke Testing (Smoke Testing) refers to: after each version or each requirement change, before the formal test, a simple verification test of the product or system to verify whether the "basic function" process of the product or system is normal . (We can understand the smoke test as a "pre-test" before performing the formal test,)
2. What is the purpose of the smoke test?
The purpose is to confirm that the basic functions of the software are normal, and the subsequent formal testing can be carried out.
(If the smoke test fails, the following tests do not have to be performed)
Knowledge point 2: What is regression testing? What is the purpose and process of regression testing?
1. What is regression testing?
Regression testing: refers to the re-testing of the old code after modification (in other words, "when a new version is released"), and then verifies that the defect has been correctly repaired, and whether the change to the system affects the previous function .
("Regression testing" is expressed in a more colloquial way: after a new version is released, test that its previous functions are still normal, and at the same time, verify whether its modified defects are normal.)
Second, the purpose of regression testing?
The purpose of regression testing: to verify that the defect has been correctly repaired, and that the change to the system has not affected the previous function.
3. At what stage does regression testing take place?
Regression testing can happen at any stage.
4. What is the process of regression testing?
1. First, in the "test strategy formulation" stage, formulate a "regression test strategy".
2. Identify new releases that require regression testing.
3. When the regression test version is released, execute the regression test according to the regression test strategy.
4. If the regression test passes, close the defect tracking list.
5. If the regression test fails, the defect tracking sheet will be returned to the developer, and the developer will re-modify the existing problems or defects. After the developer completes the modification, it will be submitted to the tester for regression testing again.
(Attachment:
1. Regression testing refers to repeating all or part of the same test before.
2. As an integral part of the software life cycle, regression testing occupies a large proportion of workload in the entire software testing process. Multiple regression tests will be performed in each stage.)