What is the difference between Smoke Test & Sanity Test?
- 10 Answers
- 9652 Views
- Qualtree Solutions, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / amit
smoke testing: It is performed by developers before
releasing the application to testing team.In this they
verify basic functionality of an application
sanity testing: After receiving the application test
engineer VALIDATES basic functionality of an application
with help of checked list to estimate stability.
Ex: For login screen
Smoke testing is only test whether the user is able to
login or not .
And Sanity testing is to test text field lenght,datatype of
text,which page it takes
| Is This Answer Correct ? | 5 Yes | 2 No |
Answer / varshab
Smoke Testing : Smoke testing is initial testing after
receiving any build.It is performed to determine application
launches,interfaces are available & responsive.If smoke
testing fails we can not go for further testing.
Sanity Testing : Sanity testing is basic functionality check
of application.After performing sanity testing we can
consider application for through testing.
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / ashish
Smoke Testing: In smoke testing we just check the major
functionality of an application.
Sanity Testing: Here we check that our application is stable
or not.means our application is in "sane" or not.
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / umesh
I need the diff between sanity and smoke, not the defnition
of smoke testing. Anyway thanks for posting answers
| Is This Answer Correct ? | 1 Yes | 0 No |
Smoke Test:
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.
Sanity testing:
Once a new build is obtained with minor revisions, instead
of doing a through regression, sanity is performed so as to
ascertain the build has indeed rectified the issues and no
further issue has been introduced by the fixes. It’s
generally a subset of regression testing and a group of test
cases are executed that are related with the changes made to
the app.
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / nataraja.cv
smoke test :testing the major functionality when ever a
build or setup or moved to testing env .so that by means of
which u will be knowing further testing is possibale or not.
| Is This Answer Correct ? | 1 Yes | 1 No |
Answer / padma.v
Sanity testing:
In which one will conduct the overall testing on the released build , Inorder to check whether it is roper for further detailed testing or not.
Smoke testing:
After the build is developed, before releasing that to the testing dept, the development team will check the overall properness of the build(i.e the major functionality of the application)
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / nasruddin shaik
Smoke Test: To verify whether the build is stable for rigorous testing.
Sanity Test: To verify major functionality when the code has changed.
Some say Sanity and smoke both are same. Some say different.
It depends on organisation to organisation and project to project.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / ravinder mehra
Smoke testing- This term came from Electronic Industry
where if ther is a shor circuit then is should produce the
smoke.
Sanity testing- This is the min no of test case that needs
to be executed before moving to the next level of testing.
Ex- If you are not able to login even after entering the
correct id/passwd that means the sanity test fails
| Is This Answer Correct ? | 1 Yes | 2 No |
Answer / chethana
The difference is Smoke testing is conducted on new Built
where as snaity test is also conducted to test basic
functionality but on already failed smoke tests.
| Is This Answer Correct ? | 0 Yes | 4 No |
I need some help. Could you solve this query i got this query the other day. Any help would be appreciated Write down any potential problems or omissions from this Fault Log Fault no: 278 Environment: Windows 98 Priority:3 Tester:Author Application: Web testing Description When i log onto the screen DF342 I should be able to delete records. However when trying to delete records an error message appears telling mw that im not authorized Response: 25 Aug: Programmer: Security needs to be setup providing access to the delete facility- No error 26 Aug:Tester: We had Security up and it doesnt seem to work- I have reopened this fault
What are the main key components in client and server applications?
DESCRIBE s/w quality assurence &s/w quality control
1. What is SQL editor,DB check points and will we use it. 2. Where will we use these things (Automation/manual)
Why testers wil prepare useracceptance testcases,system testcases and integration testcases,What is the differenece between all this test cases
What is backward compatibility testing
what is the common in all s.o.p (standaed operating procedure)?
Deep structure testing is not designed to Option 1 examine object behaviors Option 2 exercise communication mechanisms Option 3 exercise object dependencies Option 4 exercise structure observable by the use explain deep structure testing
Can anyone please give me the idea how does Requirement Tracebility Matrix, looks like ? or mail me at: ontesting@gmail.com
What were your achievements in last 2 years as a software tester(manual)
Explian equivalence partioning with anexample?
Describe any bug you remember. Plz Give some real examples
Automation Testing 
