← ClaudeAtlas

flat-test-entrypointlisted

Use when testing what a flat-layered service's trigger actually runs — the function it calls end to end against the store or files it really writes, with only the upstream transport stubbed and an idempotence test wherever a run can repeat, the containment contract of a process that outlives one run, and the framework wrapper through its own in-process harness, proving only that the wrapper reaches the work and that the work's failure arrives as its catalogue code. Where a durable-execution engine was earned, it adds the orchestration level above those, every step stubbed by its registered wire name. Not the client's own transport, which is `flat-test-service-client`, and not the data-access package's write path, which is `flat-test-persistence`. - Also when asked to test a job's or a consumer's body, a polling loop's error handling, a wrapper class, an HTTP route in front of the work it calls, a workflow's retry policy, a batch loop's termination, or what a continuation carries across runs.
wntic/pyhouse · ★ 3 · AI & Automation · score 76
Install: claude install-skill wntic/pyhouse
# Flat-Layered Test — what a trigger runs Consult `test-principles` for the testing constitution. Where this skill contradicts `test-principles`, the constitution wins. The function a trigger calls is where a flat-layered service composes everything, so its test is the one that catches wiring: what the run reads actually fits what it writes, and the aggregate counts what happened. **This skill covers the levels of wrapping around that one call, tested at each.** They are one subject because they are layers of the same invocation. The work — the body every trigger calls — is tested end to end against whatever it really reads and writes, only a remote transport stubbed; with no store and no local output nothing is running, and it is a unit test under `tests/unit/`. A process that outlives one run adds the containment test (rule 6), a framework wrapper adds the wrapper test (rule 4), and an earned durable-execution engine adds the orchestration level under `## Rules`' last subsection (`flat-entrypoint` rule 1 decides whether it is earned). ## When to use vs. neighbours - The HTTP client the body calls → `flat-test-service-client`; this level substitutes that client's transport, never the client object itself. - The tables and repository class the body writes through → `flat-test-persistence`. - The container and isolation fixtures → `flat-test-integration-setup`; the code here owns its transactions, so it takes the whole-schema wipe. - Writing the work, its containment