Write integration tests for key workflows
SkillDev toolsIntegration-testing is a skill for AI agents that reviews CI coverage, automated checks, and test strategy related to writing integration tests for key workflows. It checks whether the rule is continuously verified rather than just documented, identifying gaps where failures do not block regressions.
Available today. Use it from your connected AI after setup.
No other account needed.
Have an AI agent that can load skills, and a codebase with tests or CI workflows to review.
Then ask your AI: use the Write integration tests for key workflows skill
What your AI can do with it
- Identify key integration points: API routes calling services, services using the database,
- Review tests, CI workflows, and enforcement points for integration testing coverage
- Flag exact gaps where the rule is not automatically verified or failures do not block regr
- Explain how integration testing differs from unit and E2E testing and which tools to use
- Guide writing tests for critical paths, covering happy paths and critical error paths
Getting started
- Have an AI agent that can load skills, and a codebase with tests or CI workflows to review.
- Add the integration-testing skill to the agent's available skills.
- Ask the agent to review CI coverage or test strategy for integration tests on key workflows.
- Apply the flagged fixes: write integration tests for the critical paths it identifies.
- Consult references/rule.md for implementation details, code examples, and framework-specific guidance.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/integration-testing/SKILL.md and read by ahel’s review.
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.
Code Review
Review tests, CI workflows, and enforcement points related to Write integration tests for key workflows. Flag exact gaps where the rule is not automatically verified or where failures do not block regressions.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/testing/integration-testing
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Aug 2026
Questions
- How is integration testing different from unit testing?
- Unit tests verify individual functions in isolation and cannot catch bugs that occur when functions interact. Integration tests verify that multiple units work correctly together, catching wiring bugs before they reach production.
- Should I mock the database in integration tests?
- No. Use a real database in tests (a test database or in-memory) rather than mocking everything, so the boundary between parts of the system is exercised as it will run in production.
Advanced
- Item type
- skill
- Key
integration-testing-thedaviddias- Source
- github.com/thedaviddias/front-end-checklist