tests Copilot instructionsA
tests from andreaskarz/vibe-coding-dev-setup is a Copilot instructions file: the standing instructions GitHub Copilot reads in that repo.
mdr add andreaskarz/vibe-coding-dev-setup/.github/instructions/tests.instructions.md@git:20260211.d107b76Pins git:20260211.d107b76 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Copilot instructions
- Repository
- andreaskarz/vibe-coding-dev-setup
- Path
.github/instructions/tests.instructions.md- Versions recorded
- 1
- Latest version
- git:20260211.d107b76, committed Feb 11, 2026
- Size
- 2,317 bytes
- Repository stars
- 7
- License
- a license file GitHub does not identify
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# General Guidelines - Use these frameworks: xUnit, Moq, FluentAssertions (existing tests), xUnit Asserts (new tests). - For unit tests on Repository classes, use Squadron to create a MongoDB. - If there are more than 5 asserts to do on a result, use Snapshooter instead. - Use Theories instead of multiple tests. - Never use [MemberData]. # Test Naming Conventions - Test class names should end with "Tests" (e.g., UserServiceTests) - Test method names should follow the pattern: MethodName_Scenario_ExpectedBehavior - Use descriptive names that clearly indicate what is being tested - Name the result in the Act part either `result` or `act` when testing for exceptions. # Test Data and Setup - Mocks: Define as fields and instantiate directly if possible Pre-configure default behaviour in the constructor when appropriate Use MockBehavior.Strict as default - Instantiate the class under test in the constructor of the test class - Avoid creating the same test data repeatedly. Instead, use sample data classes. - When using Squadron, ensure to re-use the instance by creating a collection fixture # Test Structure - Follow Arrange-Act-Assert (AAA) pattern in all tests …
Read the whole file at its exact version.
How to install
mdr add andreaskarz/vibe-coding-dev-setup/.github/instructions/tests.instructions.md@sha256:f304e19e787fac6eThe line at the top of this page pins the label git:20260211.d107b76, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ngogeza6jme5argf)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in andreaskarz/vibe-coding-dev-setup/.github/instructions/tests.instructions.md since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of tests.instructions.md from somewhere else? Ask it: where did my tests.instructions.md come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Feb 11, 2026.
Watch this file (sign in, one email per new version)
Installed this file, say at tests.instructions.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (2317 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
andreaskarz/vibe-coding-dev-setup · 7 stars · license a license file GitHub does not identify · pushed 2026-02-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ngogeza6jme5argf GET https://markdownregistry.com/api/v1/resolve?ref=andreaskarz/vibe-coding-dev-setup/.github/instructions/tests.instructions.md GET https://markdownregistry.com/api/v1/blob/f304e19e787fac6e3d98b7dc2407e5cda52a1eaaeefd5d40237d4f4b3f7aa1cd
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: which agent file does what.
More from andreaskarz/vibe-coding-dev-setup
Every file in andreaskarz/vibe-coding-dev-setup