Select the smoke test case, and make the first pass for the product package entering QA

Speaking of smoke testing, everyone thinks it is very important, but how should smoke testing be done?

The smoke test is really about "smoke"

The origin of the name smoke test was originally derived from circuit board testing.Because when the circuit board is done, it will first be powered on for testing. If the board does not emit smoke, then other tests will be performed, otherwise it must be done again.The first to introduce this concept into the software product process was Microsoft Corporation. The smoke test was introduced in Microsoft to solve the quality verification problem of daily builds.When the daily build is complete, the basic functionality of the system is briefly tested with a smoke test.It can be seen that the smoke test emphasizes the verification of the main function, rather than a large and comprehensive test.The BVT test (Build Verification Testing) we often say is actually another name for the smoke test.

I believe many people will refute, BVT is BVT, and smoke test is smoke test, they are not the same thing. There are two opinions in the industry as to whether these two concepts are equal.It is more inclined to say that these two nouns are a concept.

Principles of selecting test cases for smoke testing

Smoke test refers to preliminary testing to show errors that are enough to affect the system release, so the test cases of smoke test should be a subset of the test case set, mainly to cover some systems or componentsIt is designed for important functions and mainly evaluates whether a system can operate normally.This also determines that the test case test granularity of the smoke test cannot be too small or too deep.In the design of smoking test cases, in addition to selecting the business process that is more concerned with this change, it should also include the verification of some basic questions, such as: "Is the program running?", "Is the user interface open?" or "Click eventIs it valid?