The term smoke testing is derived from the hardware industry. After making changes or repairs to a hardware or hardware component, power the device directly. If there is no smoke, the component passes the test. In software, the term "Smoke test" describes the process of validating a code change before it is embedded in the product's source tree. After examining the code, smoke testing is the most cost-effective way to identify and fix software defects. Smoke tests are designed to confirm that changes in your code run as expected and do not compromise the stability of the entire version. Smoke testing is said to be the name of Microsoft, it can be understood that the test time is short, only a bag of smoke kung fu enough. The object of the smoke test is each newly compiled version of the software that needs to be formally tested to confirm that the basic functionality of the software is normal and that it can perform subsequent formal testing, and that the performer is the version compiler. The smoke test must work in conjunction with the developer who wrote the code, because the smoke test pays particular attention to the changed code. So, when you're testing, you have to know what it is: 1, what's changed in the code. To understand the change, you must understand the techniques used, and the developer can provide instructions. 2. How the changes affect the functionality. 3. How the changes affect the dependencies of each component. In addition, before you conduct a smoke test, you should focus on the code for all changes in the code to check, which ensures that the key critical areas or weak areas identified by code inspection or risk assessment have been validated, because if it fails, the test cannot continue. Smoke tests, like the nature of regression tests, are just a test activity, not a test phase. In other words, smoke testing runs through any stage of software development.
In the actual software testing work, Smoke testing in the different stages of software development. Can be broadly divided into three categories:
Forming an integration test version before--smoke testing is a must-do for the continuous development of code to verify that each unit is successfully executed and that the test version is integrated smoothly.
After the integration test version is formed-perform Smoke testing before code check in to daily build to ensure that new or changed code does not break the integration version's completion and stability.
Correction of post-trial bug--daily build is relatively stable, the bug fix for each bug should first be Smoke testing in "clean" build, and the test pass bug fix can check in to the new D The aily build.
Smoke test (Smoking tesing)
