Home > Testing > Smoke Testing Vs Sanity Testing

Smoke Testing Vs Sanity Testing

Sl.No

Smoke Testing

Sanity Testing

1

Smoke Testing is done on the interim build to test it’s stability I.e. Build Verification testing

Sanity Testing is done during the later cycles after through regression cycles are over. I.e. toward Product release.

2

Smoke Testing is done where all the basic and major areas are tested without going too deep into functionality

Sanity Testing is done which follows a deep and narrow approach to test a particular functionality in details

3

Smoke Testing is done by developers before the build is released or by testers before accepted a build for further testing

Sanity Testing is done mostly by the testers

Advertisements
  1. Faustino Marturano
    December 9, 2010 at 2:26 am

    Nice post. Keep up the good work.

  2. June 20, 2012 at 8:02 pm

    Thank you a lot for such really valuable information found in the your blog. You can get info on http://www.softwaretestingclass.com as well with some guidelines with different way of thinking.
    http://www.softwaretestingclass.com/smoke-testing/
    http://www.softwaretestingclass.com/sanity-testing/

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: