test-data
/test-data
Keep literal values in tests self-evidently fake. Use when writing, reviewing, or modifying test code that contains literal values like timestamps, names, IDs, paths, or URLs.
- Author
- motlin ↗
- Repository
- claude-code-plugins ↗
- Licence
- Apache-2.0
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Keep literal values in tests self-evidently fake. Use when writing, reviewing, or modifying test code that contains literal values like timestamps, names, IDs, paths, or URLs.
Original author description
Keep literal values in tests self-evidently fake. Use when writing, reviewing, or modifying test code that contains literal values like timestamps, names, IDs, paths, or URLs.
How it works
- Timestamps
- Names and identifiers
- Numeric IDs
- Paths and URLs
SKILL.md preview
--- name: test-data description: Keep literal values in tests self-evidently fake. Use when writing, reviewing, or modifying test code that contains literal values like timestamps, names, IDs, paths, or URLs. --- # Test Data Guidelines Literal values in tests must be recognizable as fabricated. A reader should never wonder whether a value was copied from production. ## Timestamps Use memorable boundary dates, not specific-looking times: ```text # Bad: looks recorded from a real system 2023-11-14T22:13:20.000Z # Good 1999-12-31T00:00:00.000Z 2000-01-01T00:00:00.000Z ``` ## Names and identifiers Use the Alice/Bob/Charlie series or obviously generic names, with `example.com` (reserved by RFC 2606) for email: ```text # Bad: could be a real person, or the developer's own identity user: "jsmith" email: "john.smith@company.com" # Good user: "alice" email: "alice@example.com" ``` ## Numeric IDs Use round numbers or boundary values, not arbitrary numbers that look like real database IDs: ```text # Bad id: 8847291 # Good id: 100 id: 0 id: 2_147_483_647 id: 9_999_999 ``` ## Paths and URLs No real usernames, home directories, or system paths: ```text # Bad path: "/Users/jsmith/.config/app/settings.json" # Good path: "/tmp/test/settings.json" url: "https://example.com/api/v1/resource" ```
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · motlin/claude-code-plugins | 95 | Apache-2.0 |
| MohamedRamadanSalah/claude-qa-toolkit | 100 | MIT |
| katalon-labs/true-skills | 100 | MIT |
| DataWithBaraa/claude-code-data-engineering-skills | 90 | MIT |
Database snapshot: 13.11.2026 · package version ffbc6d603177 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90test-values
Apply when writing or reviewing any literal, fixture, id, date, path or helper argument in a .test.ts, .test-d.ts or .bench.ts file. Esposter's test values — the literals, ids, dates, paths and fixtures a test writes, and the shared data they are drawn from. - 100writing-tests
Use when writing, changing, or deciding whether to keep a test in this repo, especially in the @mcp-use/cli package. Tests assert what callers can observe (exit code, output, error codes, state, requests sent), use literal expected values, and run real code instead of mocks.… - 100magic-value-elimination
This skill should be used when the user's code contains inline string literals, unexplained numbers, hardcoded timeout values, status strings, or any value that should be a named constant or enum. Covers the elimination of magic values and the rule that every literal should have a name. - 96principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Call the code the way its users do and assert the result they observe against a literal expected value. If the test would still pass when every imported function returns undefined, rewrite the assertion or delete the test. - 100test-generator
Write unit and integration tests for existing code, covering the happy path, edge cases, error paths and boundary values, using the project's own test framework and style. Use when the user asks to add tests, raise coverage, write test cases for a function, module or endpoint, or test a bug fix. - 100test-data-builder
Test Data Builder - Auto-activating skill for Test Automation. Triggers on: test data builder, test data builder Part of the Test Automation skill category. Use when writing or running tests. Trigger with phrases like "test data builder", "test builder", "test".