Uploaded on Oct 27, 2022
The smoke testing is also known as the build validation test. It is a software testing method that includes several non-exhaustive tests to ensure that the main features of the product are working properly. The results of this test play an important role in determining whether the build can proceed to the critical testing phase.
What is smoke testing?
Devstringx
Technologies
T R A N S F E R Y O U R B U S I N E S S W I T H D E V S T R I N G X T E C H N O L O G I E
S E R V I C E S S
About
DevUstrinSgX Technologies is a Product & software development, Mobile App
development, and Automation & manual Testing, and Outsourcing service
provider dedicated to empowering businesses worldwide by providing end-
to-end capabilities from product ideation to completion. A culture of
innovation has enabled us to create cost-effective and highly scalable
software products within budget and timeline for our clients which
facilitates their progress and growth. We have served different industries
like Field Performing various types of testing Like GUI Testing, Usability
Testing, Integration Testing, User Acceptance Testing, Cross Browser
Testing, End to End Testing, Security Testing, Performance Testing,
Accessibility Testing, Compatibility Testing, etc. If you would like to discuss
our business in detail for collaboration, you can reach me directly at my
email address.
What Is Smoke
Testing
Smoke Testing is a software testing process that determines whether the deployed
software build is stable or not. Smoke testing is a confirmation for the QA team to
proceed with further software testing. It consists of a minimal set of tests run on each
build to test software functionalities. Smoke testing is also known as “Build Verification
Testing” or “Confidence Testing.”
In simple terms, smoke tests mean verifying the important features are working and
there are no showstoppers in the build that is under testing. It is a mini and rapid
regression test of major functionality. It is a simple test that shows the product is ready
for testing. This helps determine if the build is flawed to make any further testing a
waste of time and resources.
- If you are new to Smoke Testing, we have written a detailed blog on What Is Smoke
Testing? so feel free to visit & read our blog.
What Is Sanity
Testing?
Sanity testing is a kind of Software Testing performed after receiving a software build, with
minor changes in code, or functionality, to ascertain that the bugs have been fixed and no
further issues are introduced due to these changes. The goal is to determine that the
proposed functionality works roughly as expected. If sanity test fails, the build is rejected
to save the time and costs involved in a more rigorous testing.
The objective is “not” to verify thoroughly the new functionality but to determine that the
developer has applied some rationality (sanity) while producing the software. For instance, if
your scientific calculator gives the result of 2 + 2 =5! Then, there is no point testing the
advanced functionalities like sin 30 + cos 50.
- If you are interested to read a detail blog on sanity testing so We have written a detail
blog on
What Is Sanity Testing? kindly visit & read our blog.
Sanity Testing Vs Smoke
Testing
01 Smoke Testing
Smoke Testing is performed to ascertain that the critical functionalities of the program is working fine
The objective of this testing is to verify the “stability” of the system in order to proceed with more rigorous
testing This testing is performed by the developers or testers
Smoke testing is usually documented or
scripted Smoke testing is a subset of
Acceptance testing
Smoke testing exercises the entire system from
end to end
02 Sanity
Testing
Sanity Testing is done to check the new functionality/bugs have been fixed
The objective of the testing is to verify the “rationality” of the system in order
to proceed with more rigorous testing
Sanity testing in software testing is usually performed by
testers Sanity testing is usually not documented and is
unscripted Sanity testing is a subset of Regression Testing
- If you are interested to read a detailed blog on sanity testing We
have written a detailed blog on Smoke
Testing VS Sanity Testing kindly visit & read our blog.
Author
Bio
Mohit holds the Module Lead Position in Devstringx Technologies, a leading
software testing company in India. He is skilled in Agile methodology which
involves testing the software at all layers of the Test Pyramid, i.e. Unit,
Integration & reducing QE efforts in E2E Testing by automation and
documentation. He has well-versed knowledge & expertise in Functional &
Non Functional testing. "He don't break the code, He break Dev's illusion
about the code"
Contact
Us
+1 650 209 7815
[email protected]
om
www.devstringx.com
16192, Coastal Highway, Lewes, Delaware
- 19958, USA
+91 995 878 1896
[email protected]
om
www.devstringx.com
G-32, Sector-63,
Noida, Up, India,
201301
Thank
You
Comments