exact difference between smoke testing, sanity testing and
unit testing
- 7 Answers
- 14485 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
smoke testing and sanity testing both are same but some
companies the developer do the testing before the build
released to testing department that testing called as smoke
testing.
sanity testing means once the bulid was released into
testing depatment the testing people do the testing
1.the bulid can be install in the environment or not.
2.the build contain the all the navigations or not.
3.the build contain the all the main functionality or not.
4.the build contain the database connection or not.
unit is a small code in the program .the developer are do
the unit testing.
| Is This Answer Correct ? | 7 Yes | 4 No |
Answer / rashmi ranjan patra
Smoke testing and sanity testing both are same
Smoke testing means once the build was released into
testing team the testing people 1st start with smoke
testing and try to finished it asap.
1.Health check for that build to continue with this build
or not for next label testing(functional or reg testing
etc.).
Example: If lode fail,unexpected error,unable to
login,unable to link with the page etc.
2. Basic functionality are working fine or not for
Example:Able to save,update,save as,delete.
if any build issue then again new build deployed for
testing.
3. If any new Features are release for a module then we
check all the feature are release based on the feature
list plan or or not.
4. If we are getting any major bug during smoke testing
then its means that developer team are not properly doing
unit testing.
unit is a small code in the program .the developer are do
the unit testing.
| Is This Answer Correct ? | 2 Yes | 1 No |
Answer / nagk24
Smoke and Sanity are both different
Smoke:- Smoke Test is Conducted by Developer in Dev env
whether Produced Build Is Correct or not IT IS NOT A
FUNCTIONALITY TESTING
Ex:-like after hardware installed by Hardware Engineer all
the connection will be tested whether any power short
circuits,loose connections
Sanity:-Sanity will be conducted by Tester in Test env
Before going into detailed testing tester test basic and
most imp functionalitys.if there is any show stoper defects
build will be suspended
EX:-while Testing the emailwe first should test basic amd
imp functionaltys
1)able to create mail id with all valid data
2)user able to login with valid details
3)compose and able send mail to valid another user
4)able to check inbox and able to give replay
after sanity testing we do other detail(+ve and -ve data)
and usability,performance,relaible etc
| Is This Answer Correct ? | 2 Yes | 1 No |
Smoke testing & Sanity testing are almost same.
But smoke testing is done in the Developer environment
before releasing the build to test whether the build is
correct or not.
Saninty testing is a overall testing which is done in the
testing environemnt to test whether the accepted build is
suitable to test or not, proper navigation is established
or not, database is connected or not. Some companies is
also called the testing as Build Acceptance testing.
Unit testing is also done in the Developer environement to
test small small code according to the requirement.
| Is This Answer Correct ? | 0 Yes | 0 No |
@vasu you are completely wrong
developer never do sanity resting and tester never do smoke
testing
why the name came smoke? its come from real time example
when all electric wires fixed by electrician first he check
whether any smoke coming from the wires,if any he re develop
the all connections later checking if lite is working,fan is
rotating will be done
in testing point of view,while developing the software
various modules done by diff developers like login page,home
page etc .after all developing completed,all these modules
combine and produce one install file like .exe file for
deployment, this is called build.here developer done the
smoke testing on build if it is installing properly,.exe
file created or not
after smoke test done if test passed it will be deployed in
test environment.here tester test for show stoper defects
while cheking most basic and imp functionalities
correct me if i am wrong
| Is This Answer Correct ? | 1 Yes | 1 No |
Answer / m.vijaya lakshmi
Smoke testing: it is a type
of testing, in which
developer will conduct
overall testing inorder to
check the build is prope
or not.
Sanity test OR build
acceptence test: after
release the build the test
eng will test the build is
proper for conducting the
detailed testing or not.
Unit test: it is a type of
testing in which the
white box test eng will
test each and every
developed unit and
combination of unit,
unit means smallest part
of an application.
| Is This Answer Correct ? | 0 Yes | 0 No |
both testing are same the diffrence is
when the build is ready to send testing team from the dev
team the devp test the some main functionality (is this
going for further testing) is calld sanity
when the build send from the devp the tester test the some
main fun that build is going for further testing is called smoke
1.first time test the main functionality by developer is
called sanity
2.second time test the same main functionality by tester
is called smoke
| Is This Answer Correct ? | 1 Yes | 2 No |
Why Adhoc Testing is done?
What if an organization is growing so fast that fixed testing processes are impossible? What to do in such situations?
Hi, I was asked following question during a interview. Please answer it: Password field is there,we can accepts every character except underscore and semicolon. It can accept min 6 characters and maximum 12 characters. Prepare boundary value and equivalence class test cases.
How do you go about testing a web application?
Explain the Pros and Cons of testing the software by Developement team and by testing team?
How do you feel about cyclomatic complexity?
1.what is software testing?
What is "V-n-V" Model ? Why is it called as "V"& why not "U" ? Also tell at what Stage Testing should be best to stared?
What are the Use Cases?
What type of documents would you need for QA/QC/Testing?
What is Mutation Testing?
when we found problem occured in requirement while writing test case when communicate with client but they not accepting it is problem whether you continue further or not?
Automation Testing 
