Global Side Menu Width
Placeholder

Sanity & Smoke Testing

Sanity Testing

After bug fixes, sanity tests should be conducted to quickly verify that everything is functioning correctly and that the fix did not introduce new bugs. In fact, sanity tests are part of Regression Testing, where only the aspects related to the fix are checked quickly before Retesting and Regression testing.

Smoke Testing

After building the Build, small tests are conducted before running a set of Functional Tests, which saves time and money. For Smoke Tests, critical test cases are selected that impact the functionality of the system.

In summary:

  • Sanity checks: They quickly verify only the areas related to fixes or development.
  • Smoke tests: After deploying a new version to the testing environment, they check the entire system (regardless of fixes or new development), but perform quick and critical tests.