Print Page | Close Window

smoke test

Printed From: One Stop Testing
Category: Software Testing @ OneStopTesting
Forum Name: Test Plans @ OneStopTesting
Forum Discription: Discuss, Learn and Prepare better and better Test Plans for yourself.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=6125
Printed Date: 26Dec2024 at 12:19am


Topic: smoke test
Posted By: sudheer.te
Subject: smoke test
Date Posted: 15Sep2008 at 2:40pm
plz any1 just hlp me out of thisCry


Replies:
Posted By: krkrishna
Date Posted: 15Sep2008 at 3:16pm

hi sudheer

Smoke testing is a term used in http://en.wikipedia.org/wiki/Plumbing - plumbing , http://en.wikipedia.org/wiki/Woodwind - woodwind repair, http://en.wikipedia.org/wiki/Electronics - electronics , http://en.wikipedia.org/wiki/Computer_software - computer software development, and the http://en.wikipedia.org/wiki/Entertainment_industry - entertainment industry . It refers to the first test made after repairs or first assembly to provide some assurance that the system under test will not catastrophically fail. After a smoke test proves that the pipes will not leak, the keys seal properly, the circuit will not burn, or the software will not crash outright, the assembly is ready for more stressful testing.

Posted By: tossy
Date Posted: 16Sep2008 at 3:04am
Smoke testing is non-exhaustive software testing, ascertaining that the most crucial functions of a program work, but not bothering with finer details. The term comes to software testing from a similarly basic type of hardware testing, in which the device passed the test if it didn't catch fire the first time it was turned on.

-------------

Posted By: Aparna123
Date Posted: 17Sep2008 at 12:27am

Smoke test is done when the build is just prepared (fresh build) and deployed in the test environments. This is basically an ad hoc test to check roughly to make sure the major functionalities are not broken. It is the preliminary a test carried out by the QA tester. After the smoke test, the testers perform functional testing.



-------------
adm

Posted By: jimmy_vaswani
Date Posted: 01Jul2009 at 11:49pm

 

Smoke

Sanity


1

Smoke testing originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke. In software industry smoke testing is a shallow and wide approach whereby all areas of the application without getting into too deep is tested.

 

A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep.

2

A smoke test is scripted--either using a written set of tests or an automated test

 

A sanity test is usually unscripted.

3

A Smoke test is designed to touch every part of the application in a cursory way. It's is shallow and wide.

 

A Sanity test is used to determine a small section of the application is still working after a minor change.

4

Smoke testing will be conducted to ensure whether the most crucial functions of a program work but not bothering with finer details. (Such as build verification).

 

Sanity testing is a cursory testing; it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing.

5

Smoke testing is normal health check up to a build of an application before taking it to testing in depth.

 

sanity testing is to verify whether requirements are met or not

Checking all features breadth-first.



-------------
Jimmy Vaswani

Posted By: cprasenjit26
Date Posted: 21Jul2009 at 1:26pm

When a build is received, a smoke test is run to ascertain if the build is stable and it can be considered for further testing.

 

Smoke testing can be done for testing the stability of any interim build.

 

Smoke testing can be executed for platform qualification tests.

-----------------------------------------------------------

http://softwareqatestings.com - Software Testing



Print Page | Close Window