What is difference between Smoke&Sanitary Testing?
Answers were Sorted based on User's Feedback
Answer / nitin verma hcl
Hi,
Smoke Testing:- When a build is received, a smoke test is
run to ascertain if the build is stable and it can be
considered for further testing. Smoke testing can be done
for testing the stability of any interim build. Smoke
testing can be executed for platform qualification tests.
Smoke testing can be done for testing the stability of any
interim build. Smoke testing is done by developers before
the build is released or by testers before accepting a build
for further testing.
Sanity testing:- Once a new build is obtained with minor
revisions, instead of doing a through regression, a sanity
is performed so as to ascertain the build has indeed
rectified the issues and no further issue has been
introduced by the fixes. Its generally a subset of
regression testing and a group of test cases are executed
that are related with the changes made to the application.
Plz correct me if i m wrong..
Regards..
nitin9360@gmail.com
Is This Answer Correct ? | 4 Yes | 0 No |
Answer / ravindhar
Smoke testing is to find out the 'Testability' of the build
by ensuring the crucial functionalities of the application
have been delivered. This will done once build released to
QA.
Sanity testing: It is cursory testing, can be done any time
to ensure that application is working properly. mainly
focus on GUI checking, database connectivity, printer
connectivity
So both are have their own nature.
Is This Answer Correct ? | 2 Yes | 0 No |
Answer / sharman
Thousand mind, mounth and million different thoughts....
Is This Answer Correct ? | 0 Yes | 0 No |
Answer / sunil reddy
Both are validating 4 whether basic functionality of build
is stable or not for further testing
Is This Answer Correct ? | 0 Yes | 1 No |
Smoke testing is done whenver a new build comes to TCOE
team.if the smoke test pass then only teasting team proceds
for further testing i.e. basic testing done by the testing
team.
Sanity Testing:the world sanity means FRIEND whenever the
developer develops any code he do the testing by
himself.but he is not sure for what he coded so he colegie
i.e. friend developer do the testing of that code is called
sanity. actully sanity testing done by the development team.
Is This Answer Correct ? | 1 Yes | 2 No |
Answer / shrish mahajan
Smoke Testing:
The testing process in which we execute maximum number of test cases with minimum number of test data to ensure the system is ready for testing and is stable. It is done by Testers. A smoke testing is just a cursory examination of all the basic components of a s/w under test to ensure that they work.
Sanity Testing:
The testing process in which we execute maximum number of test cases with minimum number of test data to ensure that system is ready to deploy in the production environment. It is done by the Business Analysts.
Is This Answer Correct ? | 0 Yes | 1 No |
Answer / sriram
Sanity testing is nothing but Bredth level testing that
means we will touch all the functionalities we will not go
into deep, where as Smoke testing is depth testing we will
go in deep to test each and everything w.r.t the
functionality.
Is This Answer Correct ? | 1 Yes | 3 No |
Answer / sudhir
Sanity Test:Every time when a new build comes to the
testing team then firstly sanity testing is done.Sanity
consists of testing the basic functionalities of the
application.Now if any major issue is reported then the
build is rejected and sanity fails.
Now in the next build the testing is done on the reported
issue and other features are smoked out.This is smoke
testing.
Is This Answer Correct ? | 0 Yes | 3 No |
Answer / selvaa
Sanity : first conduct the sanity testing,then only go to
further testing,its means to check the basic
functionalities...
Smoke: its final testing,the particular build is going to
realease,if its capable of live environment....
kayessor Blr
Is This Answer Correct ? | 0 Yes | 4 No |
5 negative test case for lift....
5 Answers Deloitte, RBS, Wipro,
When should you begin testing?
Can anyone give me the example of 1. High severity & low Priority bug 2. Low Severity and High Priority bug 3. High Severity and High priority bug
when we are executing the test cases one bug is found.then how will u insert in to the deffect traking tool(in real time how we insert into the deffect tracking tool).please let me know the answer asap plz
If a bug has high severity then usually that is treated as high priority,then why do priority given by test engineers/project managers and severity given by testers?
What can you tell about the project if during testing you found 80 bugs in it
what is functional testing terminologies
who do sanity testing ? who do smoke testing ? plz give me correct answers.
If any bug is found in exploratory testing, then may I consider it as a test case?
What is industry standard for code coverage numbers?
Guys, can any one of u give the realtime example for Integration Testing
Hi, Anybody can explain me What is the Difference between 2- tier and 3-tier Architecture.