exact difference between smoke testing, sanity testing and
unit testing
- 2 Answers
- 5445 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / radhika jadhav
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.
Unit Testing:Testing performed on single,standalone module
or unit of code to ensure correctness of particular
module.Focuses on implementation logic,so the idea is to
write test cases for every method in the module.The goal of
unit testing is to isolate each part of the program and show
the individual parts are correct.This type of testing is
mostly done by developers.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / guest
Unit testing:-unit testing done by developer in dev
environment.In unit testing each line,statements,conditions
statements,loops and flow of the program is tested by developer.
smoke testing:-dis also done by developer in dev
environment.after system testing, developer will create
build and check whether it could be able to deploy and
stable or not.if it can't be deploy it will not be given to
testing purpose.
sanity testing:-dis is done by tester in test env.here after
build is given by developer the first thing is done by
tester is sanity testing.In this tester verify the basic and
imp functionalities without going into the deep testing.if
any show stopper defect are found it will be suspend and
given to the developer
show stopper defects are like inbox not able to open,mail
not able to send etc
| Is This Answer Correct ? | 0 Yes | 0 No |
When have you had to focus on data integrity?
Suppose " You are given a build with 5 modules to test as per the Customer request after finalization of SRS, But the SRS contains only documentation about 4 modules. On what basis you will continue the testing of 5th module." ?
15 Answers HCL, TCS,
Explain the V-Model
When a high severity issue is found in production how to handle this situation.
verfication vs validation
Draw Backs of automated testing?
1.Enlist the types of testing performed for any window in sequence? 2.Use of edit_get_list function 3.Accuracy & Precision
software testing life cycle?
How did you define severity ratings in your project?
Differences Between Whitebox testing and Blackbox testing
21 Answers CSC, IBM,
are you ready to work on new domain but you dont have any body to take help or suggestion (seniors).you are the initiator?how will you work in such cases?
write test cases forthe function f=a+b ?
Automation Testing 
