📄️ Release Lifecycle Overview
Every code change in Agent Mantis must be backed by automated tests, and those tests gate every release through the CI/CD pipeline. This section outlines the development standards, testing tiers, and enforcement gates that ensure no untested work reaches production.
📄️ Developer Responsibilities
Every contributor to the project is expected to follow these testing standards. They are enforced by the CI/CD pipeline and by code review.
📄️ Acceptance Tests (Ticket-Driven)
Acceptance tests are ticket-driven E2E tests for a specific ticket or story (e.g. a Jira story). They validate the explicit acceptance criteria for that ticket.
📄️ Regression Tests
Regression tests verify that existing features continue to work correctly after code changes. They are the primary safety net against unintended side effects.
📄️ Smoke Tests
Smoke tests are lightweight, fast-running checks that verify the most critical paths of the application are functional. They act as a first line of defense after a deployment or environment change.
📄️ CI/CD Test Gates
The GitHub Actions pipeline enforces testing at every stage of the development and release process. If any check fails — missing test coverage for a ticket, or a failing test — the pipeline fails and the action (merge, deploy, or release) cannot proceed.