quality-test-engineer

Fix flaky tests by diagnosing randomness caused by shared state, missing teardown, environment mismatches, and order dependence to ensure CI reflects real behavior. Apply debugging rules and quality gates to stabilize the suite reliably.

Choose test types based on what is being verified and the dependencies involved, selecting unit tests for isolated logic, integration tests for in-process components, and E2E tests for validating user journeys and performance requirements.

Correct mocking boundaries involve mocking external dependencies like HTTP calls, database queries, and filesystem interactions, while avoiding mocks inside the unit under test when in-process integration testing is the goal.

Yes, this approach provides framework guidance for Vitest, pytest, Playwright, Testcontainers, and k6, applying appropriate test types, mocking boundaries, and quality gates across these specific testing tools.

Enforce quality gates that prioritize test speed, behavioral assertions, stable selectors for E2E tests, and low flake rates, rather than relying solely on code coverage metrics to achieve consistent CI reliability.

Integration tests fail in CI due to environment mismatches, missing state teardown, or timeout configurations, requiring environment parity and deterministic handling of HTTP calls and database queries to stabilize results reliably.