Print Page | Close Window

Smoke Testing Printed From: One Stop Testing Category: Types Of Software Testing @ OneStopTesting Forum Name: Usability & Accessibility Testing @ OneStopTesting Forum Discription: Discuss All that is need to be known about Usability & Accessibility Software Testing and its Tools. URL: http://forum.onestoptesting.com/forum_posts.asp?TID=1314 Printed Date: 20Nov2024 at 3:23pm Topic: Smoke Testing Posted By: Suparna Subject: Smoke Testing Date Posted: 14May2007 at 5:51am The smoke test should exercise the entire system from end to end. It does not have to be exhaustive, but it should be capable of exposing major problems. The smoke test should be thorough enough that if the build passes, you can assume that it is stable enough to be tested more thoroughly. The daily build has little value without the smoke test. The smoke test is the sentry that guards against deteriorating product quality and creeping integration problems. Without it, the daily build becomes just a time-wasting exercise in ensuring that you have a clean compile every day. The smoke test must evolve as the system evolves. At first, the smoke test will probably test something simple, such as whether the system can say, "Hello, World." As the system develops, the smoke test will become more thorough. The first test might take a matter of seconds to run; as the system grows, the smoke test can grow to 30 minutes, an hour, or more

Print Page | Close Window