General points:

The main idea is to process a high-level verification of the main functionality delivered to the client:

• Time to execute depends on the build scope;

• Blocker/Critical issues are a cause for the build rejection and rollback/hotfix;

• Major/Critical issues should be created in process of verification;

• Minor&Trival issues QA can create after build verification, but should add short notes to the issues list.

Tips:

• Before starting smoke verification please check that the appropriate code version has been activated on the proper testing environment;

• After smoke testing, a proper build verification status should be set into the table;

• In case a component or feature is not ready/broken after the build – please discuss this topic with PM/DEV Lead immediately (without starting Smoke verification).