What is the difference between smoke testing and sanity testing?
Answers were Sorted based on User's Feedback
Smoke Testing is the first thing we do on AUT. Anytime the new build is deployed, smoke testing is the first step. In this we check that whether or not our aplication is running properly or not. and also we check that correct version is installed .
and Sanity testing is the functional testing and to check the most critical functionality is working or not.
First Smoke is performed and then Sanity.
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / deepthy
Smoke Testing is performed to ascertain that the critical functionalities of the program is working fine
This testing is performed by the developers or testers
Smoke testing is usually documented or scripted
Sanity Testing is done to check the new functionality / bugs have been fixed
Sanity testing is usually performed by testers
Sanity testing is usually not documented and is unscripted
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / sunita
smoke testing is initial phase testing of sanity testing.
sanity testing is testing of measure functionality testing of app.
| Is This Answer Correct ? | 1 Yes | 4 No |
Answer / kiran wale
Sanity and smoke testing are the last phase when all the integration of the modules are done.After this you have to select between these two testing.
Always have to understand that smoke testing is cursory testing of the whole software or we can say basic functionality of the software while sanity testing is in depth testing of any one module selected from the software.
Both sanity and smoke testing are implements when time is limited and software have to be launch.
| Is This Answer Correct ? | 1 Yes | 5 No |
Tell me some Adhoc testing scenarios of ebay (online auction product)?
What are the principles of software testing?
What is review checklist?
What is bottom-up approach?
Explain about Loop Testing methodology?
What will be the test cases for login phase in SIT format
what is usecase testing? when it can be applied?
How do we create a regression sute in td
A server configuration is controlled from a single web page with multiple options: ● 20 drop-down menus, with 3-4 options each. ● 5 check-boxes. ● 1 multi-select menu, with 5 options. ● 1 template selection, with 6 options: A, B, C, D, E, F. ○ When options A, B, C, D are selected, all options (#1-#3) above are available. ○ When options E, F are selected, only 10 out of 20 drop-down menus have an effect. ● Besides item #4, developers input is that all options are independent, I.e., not impacting each other. What is the required number of test configurations required in order to test the server configuration and release in good quality: a) Assuming first release. b) Assuming regression tests for release with new features not impacted by the above options. Test configuration is a complete set of options that were selected to be tested in one complete server configuration scenario. I.e, a test configuration is set of 17 or 27 specific options tested together.
What are test case formats widely use in web based testing?
How can you find dead code!!
how to see result in test director