关于软件健全性测试的困惑 [英] Confusion about sanity testing of software

问题描述

我已经阅读了几篇关于烟雾和健全性测试的帖子.所有的一切都几乎令人困惑.没有解释清楚，只是重复一下，除了一些两三个帖子，根据那两三个帖子，我得出以下结论:以下是正式流程:

I have read several posts regarding smoke and sanity testing. All are almost confusing. Neither explaining them clearly,just repeating the matter except some two or three posts and based on that two or three posts i concluded that following is the formal process:

烟雾测试(一般健康检查)---然后-->健全性测试(检查一些主要功能到有点更深层次)(专业健康检查)----------------then--------> 功能测试(更深层次的完整功能检查)

Smoke testing(generalized health checkup)---then--> Sanity Testing(checking some main functionalities to somewhat more deeper level)(Specialized health checkup)----------------then--------> Functional testing(full functionality checking at deeper levels)

我对上述概念是否正确?

Am i right in above concept?

我对何时执行理智感到困惑.第一次构建时会产生烟雾.但是什么时候执行理智呢?是仅在每次冒烟后执行还是执行每次构建都会发生一些变化(即即使不执行冒烟，因为仅在第一次构建时才执行冒烟)或者在这两种情况下?

I have confusion regarding when sanity is performed. Smoke is performed when build comes very first time. But when sanity is performed? Is sanity is performed only after every smoke OR it is performed every time build undergoes some change(i.e. even when smoke is not performed because smoke is performed only first time build comes) OR in both cases?

推荐答案

我找到了答案:

循环就像……

开发 -> 冒烟测试 -> 功能测试.

当软件发生变化时.......

When the software is changed….

重新测试 -> 健全性测试 -> 回归测试

可以在 https://www.quora.com/What-is-the-relation-between-sanity-testing-and-regression-testing.

这篇关于关于软件健全性测试的困惑的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！