qa

Full-stack QA checks centralize backend pytest, frontend Jest, ruff linting, TypeScript validation, and Playwright E2E tests into a single command to catch failures before merge. You can execute commit checks, full regression runs, and browser-level smoke tests.

Automating testing and linting for a full-stack project is best handled by running a centralized QA command that enforces pytest, Jest, ruff, and TypeScript checks with coverage thresholds and zero-error quality gates before code review.

Yes, you need pytest and Playwright installed, as the QA process requires these commands to execute backend tests and launch browser-level end-to-end workflows, alongside Jest, ruff, and TypeScript for complete full-stack validation.

Yes, you can run a fast commit check mode that executes a smoke pass with backend pytest and frontend linting plus TypeScript validation, bypassing the broader test coverage and format checks reserved for full QA runs.

TypeScript typecheck or ruff linting fails during the QA process because the system applies zero-error quality gates that catch type mismatches and formatting errors, requiring you to resolve all reported issues before passing the merge check.