test-data
Skill84 starsChanged 13 days agoMITView on GitHub
Use when a new function or a new table needs tests, to write test data with the edge cases and the expected result written first, never from production data.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- alexpalexpinne/qa-toolkittheir own version, first seen Nov 8, 2026
- vhmarquez/argotheir own version, first seen Oct 15, 2026
- katalon-labs/true-skillstheir own version, first seen Jun 23, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- katalon-labs/true-skills★ 10same name
- vhmarquez/argo★ 1same name
- alexpalexpinne/qa-toolkit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- big-reviewSkill
- contractSkill
- cost-reviewSkill
- data-productSkill
- docsSkill
- impactSkill
- incidentSkill
- knowledge-refreshSkill
- metadataSkill
- migrationSkill
- profileSkill
- pr-reviewSkill
- qualitySkill
- reconcileSkill
- toolkitSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Run the tests and report which passed.
- Distinctive: line 37
Never reads production data for a test.
- Distinctive: line 38
Never writes under the data folders.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Test data
The job: small test files with the edge cases, and the expected result decided first.
Input: the function or the table under test.
Steps
- Name the function or the table under test, and what it must do with each edge case.
- Synthetic rows from the metadata, in the source's own format. Never real data.
- The expected result first: what the output must hold, written before the code.
- Injected faults, each with its expected result: a broken line, a new column, broken bytes, a child row before its parent.
- A second delivery with drift: a renamed column that the schema check must stop.
- The fixtures beside the tests, never in the data folders.
- Run the tests and report which passed.
Output
The test files beside the tests: the input rows, the injected faults, the expected result written first, and the test that compares them.
Reads
- the metadata of the table, the file parsers of the source's format
Writes
- the fixtures of the test, and the test
Never
- Never reads production data for a test.
- Never writes under the data folders.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

