Smoke Test

Smoke Testing is a preliminary type of software testing conducted to verify whether the basic functionality of an application is working as expected. It involves running a set of simple tests to ensure that the critical components of the software are functioning properly before more extensive testing is performed.

Key components of smoke testing include:

• Basic Functionality Check: Smoke tests verify that the application launches correctly and that essential features, such as logging in, navigating through basic workflows, and displaying critical elements, are working without major issues.
• Shallow Testing: It is typically a quick and shallow form of testing, covering the most important parts of the application, rather than deep or exhaustive testing of every feature.
• Build Verification: Smoke tests are often run after a new build or update is deployed to ensure that the build is stable enough to proceed with more detailed testing, such as regression or functional testing.
• Early Detection: The goal is to identify major issues early in the development process, such as crashes, critical functionality failures, or incomplete builds, before the software undergoes further testing.
• Automation: Smoke tests can be automated to run with each new build, providing quick feedback to developers and testers on the stability of the software.

Smoke testing acts as a "health check" for the software, ensuring that it is ready for more thorough testing and preventing unnecessary testing of builds that are fundamentally broken.