What is the difference between smoke an sanity testing with
example ?
- 7 Answers
- 8889 Views
- Ness Technologies, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / balu kalkur
Sanity Testing
Narrow and deep testing. Unscripted
Take some very very important features and do deep testing
It is manually done
Smoke Testing
Scripted. Shallow and wide testing
Take all important features and do high-level testing
Build comes – write automation scripts and run the script. Thus test done automatically.
| Is This Answer Correct ? | 16 Yes | 2 No |
Smoke Testing - testing the major functionality of the application by the development team before deploy the application into testing environment is called smoke testing.
Sanity Testing- testing the major functionality of the application is called sanity testing.once the application has developed and deploy into testing environment, We can performing the sanity testing, because if the major functionality is working properly, then only we can continue further testing in the application.
Definition wise only we have difference between sanity and smoke testing but practically both are same because only testing team performing the major functionality of the application in testing environment. That why some tester in some project called as sanity testing and some tester in some project called as smoke testing.
| Is This Answer Correct ? | 3 Yes | 2 No |
Answer / vinoth
Smoke Testing : we testing major functionality is working or not. Its subset of regression testing. Ex: General Health Check up of our body.
Sanity testing: after the build release we test specifically particular piece of s/w. It subset of Acceptance testing. Ex: Special check for particular parts in our body.
| Is This Answer Correct ? | 8 Yes | 8 No |
Answer / rajesh
smoke test is done manually where as sanity testing is tested in tool using vb script
| Is This Answer Correct ? | 1 Yes | 2 No |
Smoke testing done by both tester and developer
Sanity done by only tester
Smoke testing can be automated
sanity testing can't be automated
smoke testing-to verify basic or critical existing functionality of an application before start rigorous testing
Sanity testing-To verify newly added/updated functionality
or bug fixes
IN technical terms
smoke testing excercises the entire system end to end
sanity testing excercises only a particular component of the entire system
IN general terms
Smoke is shallow and wide approach like general health
checkup
Sanity is narrow and deep approach testing like
specialized health checkup
| Is This Answer Correct ? | 0 Yes | 1 No |
Answer / manya
Smoke Testing is testing the system with respect to
main/basic functionality as soon as the application is
available for testing so as to avoid any time loss later
during thorough testing of each functionality
Sanity Testing is testing the changed or new functional
fuctionality just in order to check that at least the
change exists in the system
| Is This Answer Correct ? | 2 Yes | 9 No |
Answer / sonu
smoke testing is to the the software functionality at the developers side and developers formally testing and post in to repository after testers proceed..
sanity testing. here tester will start the testing process based on functionality..
| Is This Answer Correct ? | 1 Yes | 9 No |
What are the methods you followed, while doing black box testing???
Example for a bug not reproducible ?
Explain v-model clearly ? how it works in real time on a project?
can any one tell me the exact testing process of stand alone application, what type of testing i can perform on stand alone application and how can i track the bugs(from starting to ending), and online demo for logistics software if any one knows please send me the link.
When do you stop testing?
1.What is the risk factor problem related to project?
Before starting to write a script, how will you find the test cases that have the same functionality? And how will you maintain the code?
Defect Migration "Defect Migration" means that error is early project documents lead to errors in later documents. For example, an incorrect requirement leads to an incorrect set of speacifications, which leads to design errors, which leads to coding errors, which lead to failures when we test against user expectations. a. How will you prevent Defect Migration? b. Why do you think preventing Defect Migration is important?
What is software configuration management?
What is test out put?
there are n types of test cases how do you do?
diffrence between application testing and product testing?
Automation Testing 
