blocks|key|3824407|text|冒烟测试是在实际测试之前运行的一组基本的低成本测试。它的目的是验证构建是否成功部署，以及所有测试环境。方面正在运行，并为实际的测试过程做好了准备。它省去了你在错误的构建下测试的全部愤怒，而仅仅是意识到你一直在一个糟糕的环境中进行测试。或者错误地部署构建，可能为时已晚。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3824408|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Smoke testing is a set of basic cheap to run tests that precede actual testing. It aims to verify that the build is deployed successfully and that all test env. aspects are running and ready for the actual test process. It saves you bringing the full extent of your testing wrath down a faulty build and just realizing that you have been testing on a bad env. or erroneously deployed build possibly too late.

blocks|key|4668064|text|打开它，看看有没有烟冒出来。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4668065|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Turn it on, see if any smoke comes out.

blocks|key|4668002|text|该术语起源于hardware+repair，并已应用于软件。它的目的是快速测试应用程序在第一次运行时是否“着火”。如上所述，这只是为了确保你不会浪费一群人的时间，让他们在一些明显损坏的事情上松散。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4668003|entityMap|0|LINK|mutability|MUTABLE|url|http://www.websters-online-dictionary.org/sm/smoke_test.html^0|6|F|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

The term originates in <a href="http://www.websters-online-dictionary.org/sm/smoke_test.html" rel="noreferrer">hardware repair</a> and has been applied to software. It's intended to be a quick test to see if the application "catches on fire" when run for the first time. As stated above it's just to make sure you don't waste a bunch of folks time by setting them loose on something that's obviously broken.

blocks|key|603563|text|冒烟测试不是性能测试，也不是回归预防测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|603564|冒烟测试是一组优先级最高的全自动测试。即使你的常规构建成功了，你的产品也有可能以非常基本的方式被破坏，使其100%25不可用。烟雾测试旨在测试该级别的核心功能。没有通过冒烟测试的构建很可能会导致大部分自动化测试失败。|603565|如果冒烟测试失败，这通常意味着您因为构建不可用、无法测试等原因而失去了生产力。冒烟测试失败往往需要几个小时而不是几天的时间来立即修复。|603566|烟雾测试的重要方面是它们可以快速运行。您应该始终运行某种冒烟测试。许多团队有足够的资源在他们的日常或持续的集成构建上运行更大的测试套件(这是好的)，但是冒烟测试应该被认为是最低限度的。|603567|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Smoke testing isn't performance testing or regression prevention testing.

Smoke testing is a set of your highest priority fully automated tests. Even if your regular build succeeds, it's possible for your product to be broken in very fundamental ways that make it 100% unusable. Smoke tests are designed to test that level of core functionality. A build that doesn't pass smoke tests is very likely to fail a majority of all of your automated tests.

If a smoke test fails that generally means that you're losing productivity because the build is not usable, can't be tested, etc. Smoke test failures tend to require immediate fixes, on the order of hours not days.

The important aspect about smoke tests is that they can be run quickly. You should ALWAYS be running smoke tests of some sort. Many groups have sufficient resources to run a larger suite of tests on their daily or continuous integration builds (which is goodness), but smoke tests should be considered the bare minimum.

blocks|key|1168687|text|wikipedia+page+on+smoke+testing实际上相当不错。它包括一个指向Steve+McConnel+("Code+Complete")论文的指针，该论文发表在1996年IEEE+Software+13(4)的最佳实践部分，标题为"Daily+Build+and+Smoke+Test"。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1168688|我想说冒烟测试是单元测试和其他形式测试的前提条件:如果冒烟测试失败，那么启动单元测试就没有意义了。|1168689|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Smoke_testing|1|http://www.stevemcconnell.com/ieeesoftware/bp04.htm^0|0|V|0|3H|S|1|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

The <a href="http://en.wikipedia.org/wiki/Smoke_testing" rel="nofollow noreferrer">wikipedia page on smoke testing</a> is actually quite good.
It includes a pointer to Steve McConnel's ("Code Complete") paper in the best practices section of IEEE Software 13(4), 1996 titled <a href="http://www.stevemcconnell.com/ieeesoftware/bp04.htm" rel="nofollow noreferrer">"Daily Build and Smoke Test"</a>.

I'd say smoke testing is a precondition to unit and other forms of testing: if the smoke test fails there's no point in even starting up a unit test.

blocks|key|4667948|text|我们使用冒烟测试一词来指代对应用程序或产品进行快速基本测试以使其符合进一步测试的测试，如集成测试或功能测试。如果应用程序不能完成这些高级测试所需的一些基本工作，那么进行集成测试或其他高级测试就没有什么用处了。例如，我们有一个基于web的应用程序，我们做冒烟测试，以确保我们可以加载所有的网页，让用户登录/注销等。这些是应该与应用程序一起工作的基本事情，使其可测试。如果页面甚至不能加载，或者如果用户甚至不能登录，我们就不能在功能或集成测试方面做太多事情。我们在每个构建中都会进行冒烟测试，然后是功能和集成测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4667949|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

We use the term smoke test to refer to a testing that does quick basic tests to an application or product to make it qualify for further testing like integration testing or functionality testing. It is of little use to do integration testing or other adavanced testing if the application fails to do some of the elementary things required for these advanced testing. For instance we have a web based application and we do smoke test to ensure we can load all the web pages, lets users to login/logout etc. These are the basic things that should work with the application to make it testable. If the pages do not even load or if the users could not even login, we cannot do much with functionality or integration testing. We do smoke testing with every build followed by functionality and integration testing.

blocks|key|603597|text|冒烟测试是集成测试的第一步。作为一名开发人员，您已经将所有部分放在一起，并且在将应用程序交给您的QA团队进行“真正”测试之前，您要确保应用程序能够运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|603598|我想写更多，但MahdeTo抢先一步给了我一个正确的答案...:)|603599|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|$]]

Smoke testing is the first step of integration testing. As a developer, you've put all the parts together and you're making sure your app will run before giving it to your QA team for "real" testing.

I wanted to write more, but MahdeTo beat me to a correct answer... :)

blocks|key|4668085|text|*在进行测试之前检查应用程序的基本和关键功能称为冒烟测试。*在冒烟测试中，我们检查基本和关键功能的正向流，以检查构建是否可测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4668086|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

*checking the basic and critical feature of an application before proceeding the testing is known as smoke testing.
*In smoke testing we check the positive flow of basic and critical feature to check if the build is testable or not.

blocks|key|603808|text|我同意前面的一些答案。对我来说，冒烟测试只是一个检查，看看我的X上千个子页面和重定向是否还在工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|603809|工作表示每个子页面的状态码为"200+OK“。|603810|我尽可能晚地运行烟雾测试。在我将我的代码部署到服务器之后，在我激活这个服务器之前。|603811|今天，甚至有一个在线服务(SaaS)为我做这项工作。https://www.smest.it帮我做烟雾测试。我只在他们的主页上输入了一次我的私人域名，从那以后我的网站每天都会被检查。一点压力都没有。|offset|length|603812|entityMap|0|LINK|mutability|MUTABLE|url|https://www.smest.it/^0|0|0|0|Q|K|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@$H|V|I|W|1|X]]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

I agree with some of the previous answers. To me, Smoke Testing is simply a check if all my X thousands of sub-pages and redirects are still working. 

Working means that the status code of each sub-page is "200 OK".

I run Smoke Tests as late as possible. After I deployed my code to the server and before I take this server active.

Today there is even an online service (SaaS) doing the job for me. <a href="https://www.smest.it" rel="nofollow noreferrer">https://www.smest.it</a> helps me with Smoke Testing. I just entered once my private domain on their homepage and ever since I get my website checked daily. No stress at all.

I thought I understood that a smoke server was used for continous integration to measure the performance and test coverage of a project. Is this basically correct? What does it mean to smoke-test a program? Does it simply mean to continously apply the tests defined on the smoke server to be able to pinpoint performance degradation to a particular time frame?
<a href="https://stackoverflow.com/questions/28605496/what-is-the-difference-between-smoke-testing-and-sanity-testing">This other question</a> does describe the difference between sanity testing and smoke testing but does not ask to define smoke testing. This question is many years older than the reference question.

What is a smoke testing and what will it do for me?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我认为我理解了smoke服务器用于持续集成，以测量项目的性能和测试覆盖率。这基本上是正确的吗？冒烟测试程序是什么意思？这是否仅仅意味着继续应用smoke服务器上定义的测试，以便能够精确定位特定时间范围内的性能下降？确实描述了健全测试和冒烟测试之间的区别，但没有要求定义冒烟测试。这个问题比参考问题早了很多年。

问什么是烟雾测试?它对我有什么作用？
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问什么是烟雾测试?它对我有什么作用？EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问什么是烟雾测试?它对我有什么作用？
EN