exact difference between smoke testing, sanity testing and
unit testing
Answer Posted / 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 |
Post New Answer View All Answers
how mapp the defect id in quality center?
If automating - what is your process for determining what to automate and in what order
Can you explain exploratory testing?
What is system level testing?
What are the different levels of manual testing?
What is baseline testing?
Can Anbody please send me Daily Work status format in which I can save my daily work activity
How do you define a testing policy?
approx how long a simple website take time just for manual testing including report generation.
Can you explain equivalence partitioning?
How can you do the scalability testing?
What do you mean by Unit Testing, Integration Testing, System Testing, and User Acceptance Testing and when do you do them?
How could we start writing testcases without having the FRS,BRS Docs? My Project has some docs that are related to explain the operations which will be done in the application. It is deployed in UAT server and is a maintainance project. Tell me some technipues or best way to provide the quality to application?
Are there more defects in the design phase or in the coding phase?
How do you scope,organise and execute a test project.