Skip to main content

Testing

This section covers everything specific to writing, fixing, and shipping tests for the Octostar suite. It is not a setup guide and not a conventions dump — those live elsewhere and are kept current there:

  • Environment setup & running tests → the test repo's README.md (Prerequisites + Getting Started). Every Octostar repo owns its own setup in its README; we don't copy it here.
  • Code conventions (Page Objects, fixtures, shards, UTC, no-seed-data) → CLAUDE.md in the test repo.
  • Testing-specific knowledge (how to generate a test, debug a failure, what a good PR looks like) → these pages.

Getting started: from testable UI to shipping​

  1. Prerequisites — Environment setup. Do this once.
  2. Making your UI testable — For frontend devs. Expose the semantic hooks (testids, roles, labels) tests need.
  3. Writing your first test — Go from "I want to test feature X" to a passing test.
  4. Tools for verification — Verify your selectors against the live UI before running tests.
  5. Debugging & fixing tests — A test failed, broke, or flakes? Diagnose from evidence.
  6. Reading results — Understanding Allure dashboards and CI reports.
  7. PR checklist — What reviewers expect before you ship.