blocks|key|1193364|text|不幸的是，大多数公司都有自己的测试类型定义。来自@Mark的链接是好的。另一个像样的描述可以在here上找到。请与您的组织/SQA小组联系，了解有关这些条款和其他条款的任何文档。如果你没有，那就开始吧！|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1193365|烟雾测试|style|BOLD|1193366|1193367|旨在以粗略的方式触及应用程序的每个部分。它是浅层和wide.|unordered-list-item|1193368|Conducted的，以确保程序中最关键的功能是否正常工作，但不会为更详细的细节而烦恼。(例如构建verification).|1193369|1193370|健全性测试|1193371|1193372|专注于一个或几个功能领域。通常会缩小范围并对刚添加的特定功能进行deep.|1193373|Usually测试。|1193374|1193375|entityMap|0|LINK|mutability|MUTABLE|url|http://www.softwaretestinghelp.com/smoke-testing-and-sanity-testing-difference/^0|1B|4|0|0|0|4|0|0|0|0|0|0|5|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|D|3|E|5|6|7|18|8|@$A|19|B|1A|F|G]]|9|@]|C|$]]|$1|H|3|-4|5|6|7|1B|8|@]|9|@]|C|$]]|$1|I|3|J|5|K|7|1C|8|@]|9|@]|C|$]]|$1|L|3|M|5|K|7|1D|8|@]|9|@]|C|$]]|$1|N|3|-4|5|6|7|1E|8|@]|9|@]|C|$]]|$1|O|3|P|5|6|7|1F|8|@$A|1G|B|1H|F|G]]|9|@]|C|$]]|$1|Q|3|-4|5|6|7|1I|8|@]|9|@]|C|$]]|$1|R|3|S|5|K|7|1J|8|@]|9|@]|C|$]]|$1|T|3|U|5|K|7|1K|8|@]|9|@]|C|$]]|$1|V|3|-4|5|6|7|1L|8|@]|9|@]|C|$]]|$1|W|3|-4|5|6|7|1M|8|@]|9|@]|C|$]]]|X|$Y|$5|Z|10|11|C|$12|13]]]]

Unfortunately most companies have their own definition of testing types. The link from @Mark is good. Another decent description can be found <a href="http://www.softwaretestinghelp.com/smoke-testing-and-sanity-testing-difference/" rel="nofollow">here</a>. Check with your organization/SQA group for any documentation on these terms and others. If you don't have any, time to start!

Smoke Testing

<ul>
<li>Designed to touch every part of the
application in a cursory way. It’s
shallow and wide.</li>
<li>Conducted to ensure whether the most
crucial functions of a program are
working, but not bothering with finer
details. (Such as build
verification).</li>
</ul>

Sanity Testing

<ul>
<li>Focuses on one or a few areas of functionality. Usually narrow and deep.</li>
<li>Usually tests specific functionality that was just added.</li>
</ul>

blocks|key|1199144|text|一个很好的描述是blog|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1199145|从这个烟雾中看程序是否可以正常运行，而不是快速检查它是否工作正常。|1199146|然而，最重要的是您需要一个完整的测试计划，这是两个小案例，可以先完成，但您需要查看是否需要完整的回归测试、集成等|1199147|entityMap|0|LINK|mutability|MUTABLE|url|http://geekswithblogs.net/dthakur/archive/2004/08/24/10144.aspx^0|8|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

A good description is <a href="http://geekswithblogs.net/dthakur/archive/2004/08/24/10144.aspx" rel="nofollow">blog</a>

From this Smoke to see if the program can run than sanity for a quick check it works correctly.

However most imortant is you eed a complete testing plan and these are two small cases OK done first but you need to see if you need full regression tests, integration etc

blocks|key|1193405|text|烟雾测试|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1193406|冒烟测试是为了测试buid的平台兼容性。|1193407|健全性测试|1193408|健全性测试是回归测试的一部分。|1193409|InShort，Smoke是先做的，然后再做理智测试..因为回归测试是在获得一个带有微小更改的构建时进行的|1193410|entityMap^0|0|4|0|0|0|5|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|W|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|X|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|O|$]]

Smoke Test 

Smoke testing is done to test a buid for platform compatibility.

Sanity Test

Sanity testing is a part of regression testing.

InShort, Smoke is done first and then Sanity testing is possible..
because regression testing is done when a build is obtained with minor changes

blocks|key|4978736|text|烟雾测试：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|4978737|4978738|在这种类型的测试中，我们检查数据是否按顺序排列，以及是否在smoke测试中检查了数据流中的任何类型的间隙。|unordered-list-item|4978739|+if+workflow+breaks+fails。|4978740|检查应用程序是否已准备好进行测试。|4978741|4978742|健全测试：|4978743|4978744|添加组件后，应用程序仍在平稳运行，并在健全性测试中进行检查。|4978745|4978746|entityMap^0|0|5|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|10|8|@]|D|@]|E|$]]|$1|J|3|K|5|I|7|11|8|@]|D|@]|E|$]]|$1|L|3|M|5|I|7|12|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|13|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|14|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|15|8|@]|D|@]|E|$]]|$1|R|3|S|5|I|7|16|8|@]|D|@]|E|$]]|$1|T|3|-4|5|6|7|17|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|V|$]]

<h2>Smoke testing:</h2>

<ul>
<li>In this type of testing we check whether data is in sequence and if any type of gaps in the flow of data is checked in smoke testing.</li>
<li>If workflow breaks smoke fails.</li>
<li>To check whether application is ready for testing is also checked in smoke testing. </li>
</ul>

<h2>Sanity testing:</h2>

<ul>
<li>After adding components still the application is running smoothly and is stable is checked in sanity testing.</li>
</ul>

blocks|key|4978872|text|用简单而有意义的话：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4978873|冒烟测试：QA验证应用程序在快乐流程中工作良好，构建是否满足快乐流程的所有要求(也称为构建验收)。|offset|length|style|BOLD|4978874|健全性测试：检查应用程序中的组件在修改后仍然平稳稳定地工作，这称为健全性测试。|4978875|entityMap^0|0|0|5|0|0|6|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

In simple yet meaningful words:

Smoke Testing:
QAs validate that Application is working fine in happy flow, Build is fulfilling all the requirements of the happy flow (also called Build Acceptance).

Sanity testing:
Checking the components are still working smoothly and stable after amendment in the application is called sanity testing.

blocks|key|4978805|text|它在某些情况下可能会令人困惑，让我用一个实际的例子来回答这个问题。在我们的组织中，我们有两周的冲刺，每两周之后，我们就会得到一个新的构建。所以我们首先在建筑物上运行烟雾，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4978806|冒烟|4978807|冒烟测试是为了检查构建是否可接受，是否有任何阻挡程序可能会阻止我们进行测试，所有链接是否正常工作，是否有任何主要链接被破坏，举个非常简单的例子，假设硬件设备交付给您，您将做的第一个基本检查是插入并检查它是否正确打开，或者它是否破裂并燃烧并冒出烟雾，因此检查基本功能称为Smoke，我们在收到构建后立即进行检查。|4978808|理智|4978809|继续我上面的回答，当我们在构建上进行冒烟测试时，找到bug，识别它们，最后在两周后sprint完成，然后我们的构建被部署到生产环境中，然后在生产环境中，我们执行一个健全性测试，这是我们已经执行了两周的测试的子集。|4978810|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

It might be confusing in certain situations, well let me answer this with a practical example. In our organization we have sprint of two weeks and after every two weeks we get a new build. So we first we run smoke on the build, 

<h1>Smoke</h1>

Smoke testing is done to check if the build is acceptable or not, are there any blockers which would possibly block us from testing,are all the links working properly, is their any major link which is broken, giving a very easy example, lets say if a hardware appliance is delivered to you, the first basic check you will do is to plug it and check that it turns on properly or whether it cracks up and burns and smoke comes out of it, so checking the basic functionality is called smoke and we do it as soon as we receive the build.

<h1>Sanity</h1>

Continuing my answer above, when we have done the smoke testing on our build, found the bugs, identified them and then finally after two weeks sprint completes, then our build is deployed to production, and then on the production environment we perform a sanity test that is the subset of the testing we have been performing for the two weeks.

blocks|key|1199245|text|第一次做烟雾测试。冒烟测试:一种广泛的方法，在这种方法中，软件应用程序的所有区域都会进行测试，而不会进入deep.Is，因为在构建过程中有任何拦截器，所以您可以节省时间和精力。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1199246|健全性测试:健全性软件测试是一种狭义的回归测试，专注于软件应用程序的一个或一小部分功能领域。|1199247|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

1st done smoke testing.
Smoke testing :
A wide approach where all areas of the software application are tested without getting into too deep.Is there any blocker in that build So you can save you time and effort. 

Sanity testing : sanity software testing is a narrow regression testing with a focus on one or a small set of areas of functionality of the software application.

blocks|key|1193607|text|测试人员通常会混淆冒烟测试和理智测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1193608|烟雾测试|offset|length|style|BOLD|1193609|1193610|这是一项针对|unordered-list-item|1193611|初始测试过程的构建验证测试，用于检查被测软件是否已准备好/稳定地进行进一步测试|1193612|基于冒烟测试，决定构建是否稳定以进行进一步测试|1193613|1193614|健全性测试|1193615|执行|1193616|健全性测试是为了验证计划的功能是否按预期工作。|1193617|它是回归测试的一个子集，在我们没有足够的时间进行|1193618|测试时执行|1193619|有一篇有趣的文章，提供了有关健全性和烟雾测试的见解，以及何时执行烟雾或健全性测试Smoke+testing+vs+Sanity+testing+vs+Regression+testing|1193620|entityMap|0|LINK|mutability|MUTABLE|url|https://tutorialshut.com/smoke-testing-sanity-testing-regression-testing/^0|0|0|4|0|0|0|0|0|0|0|5|0|0|0|0|0|14|1H|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@$D|1C|E|1D|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|1F|8|@]|9|@]|A|$]]|$1|L|3|M|5|K|7|1G|8|@]|9|@]|A|$]]|$1|N|3|O|5|K|7|1H|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1J|8|@$D|1K|E|1L|F|G]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1M|8|@]|9|@]|A|$]]|$1|U|3|V|5|K|7|1N|8|@]|9|@]|A|$]]|$1|W|3|X|5|K|7|1O|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1P|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1Q|8|@]|9|@$D|1R|E|1S|1|1T]]|A|$]]|$1|12|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]]|13|$14|$5|15|16|17|A|$18|19]]]]

Often testers get confused between smoke and sanity testing.
Smoke Testing
<ul>
<li>It is a build verification test</li>
<li>Initial testing process exercised to check whether the software under test is ready/stable for further testing</li>
<li>Based on smoke test, decision is made if the build is stable for further testing</li>
</ul>
Sanity Testing
<ul>
<li>Sanity testing is done to validate the planned functionality is working as expected.</li>
<li>It is a subset of Regression Testing and performed when we do not have enough time for doing testing</li>
</ul>
There is interesting article which gives insight of Sanity and Smoke testing and when to perform smoke or Sanity testing <a href="https://tutorialshut.com/smoke-testing-sanity-testing-regression-testing/" rel="nofollow noreferrer">Smoke testing vs Sanity testing vs
Regression testing</a>

Which testing should we perform first Smoke or Sanity?

What are the differences between them?

SQA questions: Smoke or Sanity

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我们应该先进行哪种测试，冒烟还是清醒？它们之间有什么不同？

问SQA问题:冒烟还是理智
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问SQA问题:冒烟还是理智EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问SQA问题:冒烟还是理智
EN