1.Smoke testing(冒烟测试)
在一般软件公司,软件在编写过程中,内部需要编译多个版本(Builds),但是只有有限的几个版本需要执行正式测试(根据项目开发计划),这些需要执行的中间测试版本,在刚刚编译出来后,软件编译人员需要进行基本性能确认测试,例如是否可以正确安装/卸载,主要功能是否实现,是否存在严重死机或数据严重丢失等Bug。如果通过了该测试,则可以根据正式测试文档进行正式测试。否则,就需要重新编译版本,再次执行版本可接收确认测试,直到成功。
Typical characteristics of Smoke Testing:
* It exercises the entire system from end-to-end.
* It is not exhaustive but should be capable of exposing major problems.
* It ensures that the major functionality is working and the build is stable enough for further testing thoroughly.
Advantages of Smoke Testing:
* Reduced Integration Risk : Since smoke testing is carried out the integration problems are uncovered at a much earlier stage than late in the cycle.
* Finds Major Problems: A good designed smoke test can increase the probability of finding a major problem when a software is built early in the cycle. Thus you catch bugs earlier in the cycle.
* Can save time and cost – If a major problem is detected at the stage when the software is ready built, it can save huge time and cost if the same error was discovered late in the cycle.