Functional Testing – checking whether the application's behavior meets the stated requirements. The system must do exactly what is described in the specification.

Load Testing – measures how the system performs under normal and high user activity.

Release Readiness Testing – overall assessment – has all critical testing been completed, are the last bugs being fixed, is the build stable?

Regression Testing – we make sure that after changes or bug fixes, the old functionality still works as it should.

Stress Testing – testing behavior under overload: does it fail, how quickly does it recover.

Installation Testing – installation, update, removal – verification that everything works correctly in different scenarios.

Smoke Testing – a superficial check for “survivability”: does the system load, do key modules open, are there any fatal crashes?

Security Testing – searching for vulnerabilities, checking authorization, access rights, and data protection.

Configuration Testing – how the product behaves under different configuration settings (e.g., different user roles).

Sanity Testing – a quick check of specific functions after changes to ensure that they are fixed and have not broken other parts.

Compatibility Testing – does the product work on different devices, browsers, operating systems, and screens?

Data Migration Testing – transferring data between systems or versions. The accuracy, integrity, and completeness of the data are verified.

Integration Testing – testing the interaction between modules, APIs, and external systems.

Cross-browser Testing – testing in Chrome, Firefox, Safari, Edge, etc.

API Testing – testing interaction with the backend via API. Checking responses, errors, performance.

System Testing – testing the entire system as a whole, including all modules, integrations, and external dependencies.

Cross-platform Testing – evaluation of behavior on different operating systems – Windows, macOS, Android, iOS.

Mobile Testing – testing behavior on mobile devices: adaptability, orientation, gestures.

UI/UX Testing – evaluation of the visual interface and compliance with UX guidelines. Checking whether it is convenient for the user.

Localization Testing – checking translations, number formats, dates, cultural adaptation.

Exploratory Testing – intuitive exploration of the system without predefined scenarios – often finds unexpected bugs.

Usability Testing – testing with users – how understandable and convenient the product is.

Accessibility Testing – assessing the accessibility of a product for people with disabilities – testing according to WCAG standards.

Ad-hoc Testing – informal, spontaneous testing without preparation. Often used in the final cycles.

Performance Testing – testing the speed, responsiveness, and stability of the system under load.

Acceptance Testing (UAT) – final testing by the customer or business. Confirmation that the product is ready for release.

End-to-End Testing – testing the entire user journey – from registration to goal completion (e.g., order, purchase, report).