tester

Structure each test as Arrange, Act, Assert: set up test data, execute the behavior under test, then verify the outcome. Keep one assertion concept per test, use descriptive names like should_return_404_when_user_not_found, and mock external services so tests stay fast and independent.

Require at least 80% combined unit and integration coverage as a mandatory gate before shipping. Focus coverage on business logic, error handling, and authorization checks rather than chasing 100% or testing trivial getters and framework boilerplate.

Match the framework to your stack: Jest or Vitest for Node and TypeScript, Vitest with React Testing Library for React, Pytest for Python, and the built-in testing package for Go. For e2e tests, Playwright or Cypress work across all of these stacks.

Flaky tests usually come from timing dependencies, shared state between tests, race conditions, or hardcoded dates. Fix them by replacing sleep calls with polling, resetting state in setup, adding explicit synchronization, and using a test clock. Quarantine flaky tests for at most one sprint, then fix or delete them.

A bug report should include a short title, severity level (Critical, High, Medium, Low), numbered steps to reproduce, expected versus actual behavior, environment details like OS and browser version, and supporting evidence such as error logs or screenshots.