冒烟测试和系统预测试的区别?

如题,冒烟测试就是在每日build建立后对系统的基本功能进行简单的测试,而系统预测试也是先验证项目某个版本的基本功能是否已经实现,2者有着什么区别呢?
是不是冒烟测试是DAILY BUILD,即每天都要做的,而预测试是一个版本提交后才做?

==

测试重点不一样

冒烟集中于新增功能是否能够使用,为后面的系统预测是做铺垫,防止因为一些严重问题而影响后期测试的计划

具体问题具体处理,冒烟一般是daily build后立即做,预测就要看时间安排了

===

SMOKE & SANITY TESTING

There are two type of test types, Smoke and Sanity.  What they are exactly? Here we go.....

The general definition (related to Hardware) of Smoke Testing is:
Smoke testing is a safe harmless procedure of blowing smoke into parts of the sewer and drain lines to detect sources of unwanted leaks and sources of sewer odors.

It it is related to s/w, the definition is Smoke testing is non-exhaustive software testing, ascertaining that the most crucial functions of a program work, but not bothering with finer details.

Sanity testing is a cursory testing; it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing. It normally includes a set of core tests of basic GUI functionality to demonstrate connectivity to the database, application servers, printers, etc.
原文地址:https://www.cnblogs.com/bukudekong/p/2125249.html