Active Topics Memberlist Calendar Search Help | |
Register Login |
One Stop Testing Forum : Types Of Software Testing @ OneStopTesting : Usability & Accessibility Testing @ OneStopTesting |
Topic: Smoke Testing |
|
Author | Message |
Suparna
Groupie Joined: 28Apr2007 Online Status: Offline Posts: 72 |
Topic: Smoke Testing 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 Post Resume: Click here to Upload your Resume & Apply for Jobs |
|
IP Logged | |
Forum Jump |
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
© Vyom Technosoft Pvt. Ltd. All Rights Reserved.