what is the Exact difference between Sanity and Smoke testings
Answers were Sorted based on User's Feedback
Answer / shiva
Both are tested by testers.
When build is at the initial phase of STLC, say build No 1, then smoke testing is conducted to ensure build is suitable for further testing, where major functionality, critical areas, show stopper TC's are tested.
When build is at the middle or final phase of STLC, say build No 20-100+, then sanity testing is conducted to ensure reported defects in the previous cycle is fixed and tester can go run for regression kind of testing.
| Is This Answer Correct ? | 14 Yes | 4 No |
Answer / gagan paigoriya
Sanity testing:- 1- Unscripted, Narrow and deep Testing
2- Review Very Very important features and do deep testing.
Smoke Testing:- 1- Scripted, Shallow and wide Testing
2- Review all important features and do wide testing.
| Is This Answer Correct ? | 1 Yes | 1 No |
Answer / rohit lamsonge
smoke: Testing the Basic and critical feature immediately when we get build before doing r in-depth testing. If basic feature are not working there is no reason to do in-depth testing.
Sanity: sanity is nothing but the part of smoke testing. but one step ahead. ex: For GMAIL, if testing basic functionality of compose, send mail, inbox is smoke then testing the send mail con be forwarded , replay is sanity (one step ahead).
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / varsha saxena
Sanity and Smke are done by Testers only.
Sanity is a small set of test cases executed to check if
the built is ready to test or not.
Smoke is a small set of regression test set, to check if
built is ready to release. Once done, it is reday to go to
UAT or production
| Is This Answer Correct ? | 0 Yes | 6 No |
Answer / narasimha
Sanity means one will conduct overall testing on the
released build, to confirm whether the build is proper or not.
Smoke means before releasing the build developers will check
the same or not.
| Is This Answer Correct ? | 2 Yes | 13 No |
Our software designers use UML for modeling applications. Based on their use cases, we would like to plan a test strategy. Do you agree with this approach or would this mean more effort for the testers.
If there is no sufficent time for testing & u have to complete the testing then what will u do?
what is water fall model?
I am a B.COM graduate. I have studied all the theorotical aspects of manual testing. How can i get in to testing without practical exp. And even if i manage to get a job, i want to know whether i will be able to do my job, being i am new to software field.
what is the format for usecase?
what is the entry and exit criteria for system testing in v model
what is the challenging position faced in the testing not in point of management point of view it must be in the point of while testing the application?
is retesting and regression same
Can u specify one Deadlock or Processlock issue in a client server application?
What r the different types of testcase techniques?
what are the advantages of manual and automation testing ? and which one would u term as efficent testing and effective testing ?pls do reply thankx in advance its urgent
Can you please provide me the answers for google page, yahoo home page, elevator, traffic signals. Thanks, Rama