烟雾测试是一种初步测试，旨在揭示严重足以拒绝潜在软件发布的问题。它通过选择并运行覆盖组件或系统最重要的功能性的子集测试用例，来确认程序的关键功能是否正确工作。例如，基本问题如程序是否运行、是否打开窗口、点击主按钮是否有反应等。如果关键功能不工作或关键错误尚未修复，团队将不会浪费时间进行安装或进一步测试。
In computer programming and software testing, smoke testing is a preliminary to further testing, intended to reveal simple failures severe enough to reject a prospective software release. In this case, the smoke is metaphorical. A subset of test cases that cover the most important functionality of a component or system are selected and run, to ascertain if the most crucial functions of a program work correctly.For example, a smoke test may ask basic questions like “Does the program run?”, “Does it open a window?”, or “Does clicking the main button do anything?” The purpose is to determine whether the application is so badly broken that further testing is unnecessary. As the book “Lessons Learned in Software Testing” puts it, “smoke tests broadly cover product features in a limited time … if key features don’t work or if key bugs haven’t yet been fixed, your team won’t waste further time installing or testing”.
Smoke testing performed on a particular build is also known as a build verification test.
A daily build and smoke test is among industry best practices. Smoke testing is also done by testers before accepting a build for further testing. Microsoft claims that after code reviews, “smoke testing is the most cost effective method for identifying and fixing defects in software”. In Microsoft’s case, a smoke test is the process of validating code changes before they are checked into source control.
Smoke tests can either be performed manually or using an automated tool. When automated tools are used, the tests are often initiated by the same process that generates the build itself.
Smoke tests can be broadly categorized as functional tests or unit tests. Functional tests exercise the complete program with various inputs. Unit tests exercise individual functions, subroutines, or object methods. Both functional testing tools and unit testing tools tend to be third-party products that are not part of the compiler suite. Functional tests may be a scripted series of program inputs, possibly even with an automated mechanism for controlling mouse movements. Unit tests may be separate functions within the code itself, or driver layer that links to the code without altering the code being tested.
扫一扫
572
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
