Check whether a passing test relies on another task's database setup
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 agent.
Use cases
Show all 8Show fewer
Methods
Compare a shared database against a fresh one before trusting a passing test
Steps
- Read the linked Python reproduction first. It needs Git and Python 3.9+ with sqlite3 and only creates a temporary test repository, two Git worktrees and SQLite files.
- Keep both worktrees (A and B) on the same commit, point them at the same SQLite file and leave out B's own setup step.
- Run B's check before anything fills the database and note that it fails.
- Fill the shared database from A and run B's unchanged check again. It now passes even though B never set up its own data.
- Point B at a separate empty SQLite file. The same check fails again; after B fills its own file, it passes. Confirm neither worktree has changes.
- In real reviews, record the commit, command, exit status, database location and which task set it up, and rerun with a fresh database owned by the task before trusting a green result. Keep connection strings and credentials out of reports, and never reset someone else's shared data.
- Note: Summarized from Ryan Graham's (Zozo HQ) method and reproduction. It shows fixture contamination only, not concurrency or app correctness.
Run this method with your agent
Download .mdCopied 0
--- name: "check-shared-database-before-trusting-worktree-tests-method" description: "Use when you need to Check whether a passing test relies on another task's database setup. Compare a shared database against a fresh one before trusting a passing test" --- # Compare a shared database against a fresh one before trusting a passing test Job: [Check whether a passing test relies on another task's database setup](https://aiagents.org/canai/check-shared-database-before-trusting-worktree-tests) ## Need - AI agent ## Steps 1. Read the linked Python reproduction first. It needs Git and Python 3.9+ with sqlite3 and only creates a temporary test repository, two Git worktrees and SQLite files. 2. Keep both worktrees (A and B) on the same commit, point them at the same SQLite file and leave out B's own setup step. 3. Run B's check before anything fills the database and note that it fails. 4. Fill the shared database from A and run B's unchanged check again. It now passes even though B never set up its own data. 5. Point B at a separate empty SQLite file. The same check fails again; after B fills its own file, it passes. Confirm neither worktree has changes. 6. In real reviews, record the commit, command, exit status, database location and which task set it up, and rerun with a fresh database owned by the task before trusting a green result. Keep connection strings and credentials out of reports, and never reset someone else's shared data. 7. Note: Summarized from Ryan Graham's (Zozo HQ) method and reproduction. It shows fixture contamination only, not concurrency or app correctness. ## Credit Method author Ryan Graham, Zozo HQ Source: https://github.com/openai/codex/discussions/59765
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/check-shared-database-before-trusting-worktree-tests - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "check-shared-database-before-trusting-worktree-tests",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}