chore(tooling): establish testing and project guidance #2
No reviewers
Labels
No labels
area/backend
area/frontend
area/tooling
kind
build
kind
chore
kind
ci
kind
docs
kind
feat
kind
perf
kind
test
size
l
size
m
size
s
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
viacheslavshuka/quorum!2
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/testing-and-agent-guidance"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Establish shared project guidance and a reusable testing skill so agents follow explicit rules for useful assertions, test isolation, Python maintenance, and API contracts.
CLAUDE.mdlinks toAGENTS.mdso both entry points use the same guidance.The testing skill keeps its core rules concise and loads focused references for pytest, Hypothesis, async API and PostgreSQL tests, coverage, and mutation testing. The API guidance requires OpenAPI declarations that match runtime behavior and support Schemathesis and generated TypeScript.
Add pytest-asyncio, HTTPX, Testcontainers with PostgreSQL support, and Schemathesis as development dependencies. Configure strict asyncio mode with function-scoped loops. Use compatible-release constraints consistently and add
uv.lockfor reproducible installation. The changes affect contributor guidance and development tooling.Validation
git diff --checkpassed.uv lock --check --offlinepassed.Review guidance
Read
AGENTS.mdand.agents/skills/testing/SKILL.mdfirst, then the references relevant to their rules. The second commit contains the dependency and asyncio configuration changes, including the generated lockfile.