|
|
原帖由 fish55 于 2009-7-28 12:38 发表 
我理解的冒烟测试为了验证被测软件是否ready for formal test, 我理解的对吗?如果这样,那就大概run 一下applicaiton不就行了吗?
你的理解基本正确。但smoke test最好是能够重复的，因为会频繁的执行，如果能够自动化更好。它的目的就是要保证新build出来的软件可以经得住基本的测试，主要功能不要有问题。所以一般smoke test的用例会是测试软件最基本的功能，可以是regression test用例的一个子集。下面一些内容来自wiki，可以参考。
Smoke testing is done by developers before the build is released to the testers, or 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 software testing, a smoke test is a collection of written tests that are performed on a system prior to being accepted for further testing. This is also known as a build verification test. This is a "shallow and wide" approach to the application. The tester "touches" all areas of the application without getting too deep, looking for answers to basic questions like, "Can I launch the test item at all?", "Does it open to a window?", "Do the buttons on the window do things?".
The purpose is to determine whether or not the application is so badly broken that testing functionality in a more detailed way is unnecessary. These written 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. |
|
/1 
关于我们
楼主
发表于 2009-7-24 22:52:59
