What problem does it solve? Developers working in the Operately repository often struggle to know where a new test file belongs, which case module to use, and how to run only the relevant tests without triggering slow full-suite runs. This Skill encodes the repository's test layout conventions, naming rules, and execution commands so tests are created and run correctly the first time. ## Core Features & Use Cases - Test placement rules: Maps source files to test locations via .projections.json conventions, enforcing one test module per API endpoint and steps modules for feature, CLI, and MCP e2e tests. - Case modules and patterns: Documents when to use DataCase, TurboCase, ConnCase, FeatureCase, the Factory pattern, feature step modules, and email assertions. - External API auth specs: Explains how to add QuerySpec/MutationSpec modules, register them in queries.ex/mutations.ex, and validate token auth via auth_test.exs. - Targeted test execution: Shows how to run single files with make test FILE=..., run feature tests in CI mode with CI=true, and avoid slow suite-wide commands. - Use Case: When adding a new documents/list_versions API endpoint, use this Skill to create the matching TurboCase test, add an external QuerySpec, register it, and run only the affected test files. ## Quick Start Ask the agent to write and run a test for a specific Operately module or API endpoint following the repository's testing conventions.
