What is included in the critical test set?

The critical test suite includes checks of the application's basic functionality, without which its use is impossible or severely limited. These are tests that must pass successfully for the build to be considered minimally stable.

Typically include:

1. Application launch and shutdown: Successful installation (if necessary), error-free startup, proper shutdown.
2. Authorization/Authentication: Checking login with valid and invalid credentials, registering a new user (if applicable), password recovery.
3. Key user scenarios (Happy Path): Testing the execution of main, most frequent user actions. For example:
   • For an online store: search for a product -> add to cart -> checkout -> payment.
   • For a social network: create an account -> post -> comment.
4. Access to main sections/pages: Checking navigation through key parts of the application.
5. Basic data operations: Creating, viewing, editing, deleting main entities (CRUD operations), if the application involves data handling.
6. Integration with critically important external systems: If the application depends on other services (payment systems, external APIs), their basic interaction is checked.

The goal of the critical test suite is to quickly determine whether the build is suitable for further extended testing or release.