saroj vidyarthi

• Oct 3rd, 2005

 

This is done to check whether the basic functionality of new build (frequency of build may be weekly, monthly etc) is working fine or not.

arulmozhi

 Profile Answers by arulmozhi 

• Oct 5th, 2005

 

To check maximum number of functionalities with minimum number of test cases. Only important functionalities need to be tested(checking show stoppers.)

cat123

 Profile Answers by cat123 Questions by cat123

• Oct 7th, 2005

 

test which is intended to verify that software is not crashing in major areas. These tests do not look for accuracy in the functionality, but simply that sunctionality can be accessed. Exe., Does the File ->Open bring up a window to open file

chandra shekar

• Oct 12th, 2005

 

saroj vidyarthi Wrote:

This is done to check whether the basic functionality of new build (frequency of build may be weekly, monthly etc) is working fine or not.

mindq

• Oct 13th, 2005

 

during this test test engineer reject build with reason, when that build is not working before testing process

bharathp

 Profile Answers by bharathp 

• Jul 18th, 2006

 

smoke testing is Nothing But Executing all the basic functionalities of the Apllication 

Bharath.P

kavitha Ganesan

• Jul 19th, 2006

 

A smoke test is a shallow and wide approach whereby all areas of the application without getting into too deep is tested.

A smoke test is designed to touch every part of the application in a cursory way.

GEETHATHIRAVIAM

• Aug 11th, 2006

 

smoke testing is the basic testing to test the functionality of the build.

G.D.S.Prasad

 Profile Answers by G.D.S.Prasad Questions by G.D.S.Prasad

• Dec 21st, 2006

 

Hi,

Smoke testing is done after every build , to find out whether all the links and screens are displayed properly without any problem. It is done just to make sure that the build is proper or not. It is also known as Build Verification Testing (BVT).

If the build passes the smoke test then only it is further tested.

Regards

Prasad

deepthi

• Apr 11th, 2007

 

once the development team handsover the application for testing we test the application whether it is good enough for system testing or not and at this point we even take the go/no go decision depending up on the quality of the product.

        this is called smoke testing.