testing-aqa

Autotest goal and scenarios Environment and access Selected framework and versions Test data and cleanup strategy Data and fixtures Stability requirements (flake rate) Artifacts requirements (screenshots/video/trace) Retry rules (if allowed) </input_requirements> Tests are independent and isolated Each test has a clear success criterion Use stable selectors and patterns Assert business-meaningful states, not implementation details Minimize duplication via POM/fixtures Parameterize checks for variable data Separate UI, API, and integration tests </design_rules> Tests are deterministic and repeatable Failures are localized (clear failure reason) Flakes are fixed, not masked Collect artifacts on failure (screenshot/video/trace) Tests should be fast and parallelizable Retries are limited and documented </execution_rules> Critical user paths Authorization and access control Core CRUD operations Errors and validation Do not use sleep instead of state-based waits Do not depend on unstable selectors Do not mix multiple scenarios in one test Do not make tests depend on execution order Do not share mutable state between tests </do_not> Page Object Model with isolated actions and assertions Fixtures for data and auth Explicit waits for UI state Selectors by role/data-testid/aria </example_patterns>