Smoke Testing is performed after software build to find that the critical functionalities of the web application or software is working fine. Smoke testing executed "before" any detailed functional or regression tests are executed on the software build. The purpose is to reject a badly broken application, so that the QA team does not waste time installing and testing the software application.
Smoke testing is normal health check up to a build of an application before taking it to testing in depth. Smoke testing also known as Verification Testing.
Some facts about smoke testing:
Smoke testing is normal health check up to a build of an application before taking it to testing in depth. Smoke testing also known as Verification Testing.
Some facts about smoke testing:
- A smoke test is a subset of the test cases that is typically representative of the overall test plan.
- Smoke tests are good for verifying proper deployment or other non invasive changes.
- They are also useful for verifying a build is ready to send to test.
- Smoke tests are not substitute for actual functional testing.
Posts
