What is smoke testing and which components are tested within its framework?

Smoke testing (smoke testing) is a quick check of the main functions of an application to ensure that critical components work correctly and do not contain blocking defects after build or deployment / code changes. The goal is to determine the suitability of the build for further detailed testing. If the smoke test fails, the build is rejected.

Typically, smoke testing checks:

• Installation / Deployment: Successful installation of the application or deployment of a new version.
• Authorization / Authentication: Ability to log in with valid credentials.
• Main business processes: Basic and critical usage scenarios (e.g., creating an order, adding a product, sending a message).
• Interface: Loading of main pages, availability of key elements (buttons, input fields).
• Connection to database or external services: Basic functionality of integrations.
• Error logging: Checking that critical errors are recorded.

Smoke testing is performed at the earliest stages after receiving a new build, often before regression or functional testing. It helps save time and resources by quickly identifying major problems. It can be performed manually or automatically.