Smoke testing & Sanity testing

Smoke testing

  1. Smoke testing is performed to certain that the critical functionalities of the program is working fine.
  2. The objective of this testing is to verify the stability of the system in order to proceed with more rigorous testing.
  3. This testing is performed by the developers or testers.
  4. Smoke testing is usually documented or scripted
  5. Smoke testing is a subset of acceptance testing
  6. Smoke testing exercise the entire system from end to end
  7. Smoke testing is like general health check up

Sanity testing

  1. Sanity testing is done to check the new functionality bugs have been fixed.
  2. The objective of the testing is to verify the rationality of the system in order to proceed with more rigorous testing.
  3. Sanity testing usually performed by the testers.
  4. Sanity testing is not documented and unscripted
  5. Sanity testing is subset of regression testing
  6. Sanity testing exercises only the particular component of the entire system
  7. Sanity testing is specialized health check up