Skip to main content

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.

Rules​

  1. Every code change requires a test. Whether committed via a pull request or directly to main, every change must have an accompanying acceptance test.
  2. Every new function, component, or endpoint must have a corresponding test that validates its expected inputs, outputs, and error handling.
  3. Commits always deploy to dev. Developers may commit directly to main or via a pull request. Every commit triggers a deployment to the dev environment — this is never blocked.
  4. Acceptance tests run on dev and gate promotion. After the build is deployed to dev, the acceptance test suite runs automatically against the dev environment. If any acceptance test fails, the build cannot be promoted to UAT or production.
  5. Tests must pass before release. The release pipeline runs regression and smoke suites against higher environments. If any test fails, the release is halted.

What This Means in Practice​

  • When you pick up a ticket, plan the test alongside the implementation — not as an afterthought.
  • Name your acceptance test spec with the ticket key (e.g. MAN-452-environment-variable-limits.spec.ts) so the pipeline can verify coverage automatically.
  • Every commit deploys to dev automatically. Your acceptance tests run there — if they fail, the build is blocked from promotion.
  • A ticket is not considered complete until its acceptance test is written, passing, and merged.

Further Reading​