integration-testing SKILL.md skillA
integration-testing from thedaviddias/front-end-checklist is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add thedaviddias/front-end-checklist/integration-testing@git:20261004.4b0ddb9Pins git:20261004.4b0ddb9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- thedaviddias/front-end-checklist
- Path
skills/integration-testing/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261004.4b0ddb9, committed Oct 4, 2026
- First version recorded
- May 29, 2026
- Size
- 2,057 bytes
- Repository stars
- 74,516
- License
- MIT
Use when reviewing CI coverage, automated checks, or test strategy related to Write integration tests for key workflows. Focus on whether the rule is continuously verified, not just documented.
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
# Write integration tests for key workflows Unit tests verify individual functions in isolation, but they can't catch the bugs that occur when those functions interact — a perfectly correct validation function and a correct database function can still fail when wired together incorrectly. Integration tests catch these wiring bugs before they reach production, where they're expensive to diagnose. ## Quick Reference - Integration tests verify that multiple units work correctly together - Test at the boundary where different parts of your system meet - Use a real database in tests (test DB or in-memory) rather than mocking everything - Test happy paths and the most critical error paths ## Check Identify the key integration points in this codebase — where API routes call services, where services interact with the database, and where components interact with state management. Are these tested? ## Fix Write integration tests for the identified critical paths, testing the interactions between components rather than each in isolation. ## Explain Explain integration testing, how it differs from unit and E2E testing, and what tools to use for API and component integration tests. …
Read the whole file at its exact version.
How to install
mdr add thedaviddias/front-end-checklist/integration-testing@sha256:23fb77a077fdb160The line at the top of this page pins the label git:20261004.4b0ddb9, 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_frdnmro3ujewko5t)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 29, 2026 and Oct 4, 2026, about one every 128 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261004.4b0ddb9 latest | 2026-10-04 | 4b0ddb9 | 2,057 B | A | view · diff |
| git:20260529.7c05904 | 2026-05-29 | 7c05904 | 2,063 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2057 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
thedaviddias/front-end-checklist · 74,516 stars · license MIT · pushed 2026-10-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_frdnmro3ujewko5t GET https://markdownregistry.com/api/v1/resolve?ref=thedaviddias/front-end-checklist/integration-testing GET https://markdownregistry.com/api/v1/blob/23fb77a077fdb1605313085c683dac04978e747b46f7337d6d8f253e1f524019
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: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from thedaviddias/front-end-checklist
Every file in thedaviddias/front-end-checklist