Diference between sanity & somke testing?
Answers were Sorted based on User's Feedback
Answer / rohit
Sanity Testing:It's generally is a subset of regression
testing.It is in-depth testing of that module for which the
errors have been rectified. If the error is in one function
of the module we will test that function as well as the
whole module.
Smoke Testing: It is done to ascertain if the build is
stable and can be used for further testing.it is done to
find wheter the basic functionality of the program is
stable.
Is This Answer Correct ? | 2 Yes | 0 No |
Answer / guest
i think both are same.
sanity testing: After receiving the build, testers has to go
for sanity testing, in order to ensure that build is stable.
Shankar
Is This Answer Correct ? | 1 Yes | 0 No |
Answer / sam
SMOKE TESTING:
Smoke testing originated in the hardware testing practice
of turning on a new piece of hardware for the first time
and considering it a success if it does not catch fire and
smoke. In software industry, smoke testing is a shallow and
wide approach whereby all areas of the application without
getting into too deep, is tested.
A smoke test is scripted, either using a written set of
tests or an automated test
A Smoke test is designed to touch every part of the
application in a cursory way. It’s shallow and wide.
Smoke testing is conducted to ensure whether the most
crucial functions of a program are working, but not
bothering with finer details. (Such as build verification).
Smoke testing is normal health check up to a build of an
application before taking it to testing in depth.
SANITY TESTING:
A sanity test is a narrow regression test that focuses on
one or a few areas of functionality. Sanity testing is
usually narrow and deep.
A sanity test is usually unscripted.
A Sanity test is used to determine a small section of the
application is still working after a minor change.
Sanity testing is a cursory testing, it is performed
whenever a cursory testing is sufficient to prove the
application is functioning according to specifications.
This level of testing is a subset of regression testing.
Sanity testing is to verify whether requirements are met or
not, checking all features breadth-first.
Is This Answer Correct ? | 1 Yes | 0 No |
Answer / rahul
Sanity testing: A tester conduct testing on the received initial build to verify the basic functionalities of our application.It is also known as Build verification testing.
Smoke testing: A tester are validating the negative and positive functionalities of a application.
Is This Answer Correct ? | 0 Yes | 1 No |
Answer / swati purohit
smoke testing: consider as a positive testing.In this
testing will do short testing.
Sanity testing : consider as a negative testing .sanity
testing is to verify whether requirement are met or
not ,checking all features breadth- first.
Is This Answer Correct ? | 0 Yes | 2 No |
Answer / rajesh.pothina
Sanity Testing:
Initial testing is called as sanity
testing. After completing the test initially we will test
the givem module is that up to the mark or no that is
called sanity testing.
Smoke Testing:
Smoke testing is nothing but before
releasing the project the final testing is done that
testing is called smoke.
Based on the organization this will we wise versa in some
organizations the name will be in opposite but the theme is
the same.
Is This Answer Correct ? | 2 Yes | 7 No |
When you will raise defect? before defect raising what you will do?
what is user interface testing?
what are the possible test cases for online jobs search portal..if its a job seeker module and any 1 if u had worked on this proj pls share the bugs with sev and priority pls frends i need replies for these queries ..thanks in advance
What is Benchmark Testing
What is the Major difference between Sanity and Smoke Testing
Difference between SIT and UAT
How to test Reports manually?
Tell me abuot your daily activities as a test engineer.
Explain the difference between alpha testing and beta testing.
1.exactly when we go for regression testing?why? 2.what is compatibility testing?what defect u found while testing give example? 3.how many test cases you write and execute per day?
My questions are- 1. If we have 1 week time in hand what will be the approch of testing. 2. If we have very lesstime in hand then how we will do the regration testing. 2. When there is a change in requirement in module A then what should be the approch to change in that module and in other module like B,C etc an whow we update the test case pls explain the scenario in detail. 3.How do you confirm that for perticular funtionality all the test cases has been written. Thanks
what is white box testing and what is the teckniques