integration-testing
/integration-testing
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.
- Author
- thedaviddias ↗
- Repository
- front-end-checklist ↗
- Licence
- MIT
- Last repository change
- 06.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 06.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author description
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.
How it works
- Quick Reference
- Check
- Fix
- Explain
- Code Review
SKILL.md preview
--- name: integration-testing description: "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." metadata: category: testing priority: high difficulty: intermediate estimatedTime: "30" source: frontendchecklist.io url: https://frontendchecklist.io/rules/testing/integration-testing --- # 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. ## 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/rules/testing/integration-testing
Files in this package (2)
- SKILL.md 2 KB
- references/rule.md 4 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · thedaviddias/front-end-checklist | 100 | MIT |
| elastic/integration-skills | 100 | Apache-2.0 |
| s-morgan-jeffries/apple-mail-fast-mcp | 100 | MIT |
| kid-sid/codex-spellbook | 100 | MIT |
| MARUCIE/openclaw-foundry | 95 | MIT |
| Tyler-R-Kendrick/agent-skills | 95 | MIT |
| OKHP3/skillz | 90 | MIT |
| Amey-Thakur/AI-SKILLS | 90 | MIT |
Database snapshot: 13.11.2026 · package version 2911cdaa4e74 (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
- 100e2e-testing
Use when reviewing CI coverage, automated checks, or test strategy related to Implement end-to-end testing. Focus on whether the rule is continuously verified, not just documented. - 100mobile-testing
Use when reviewing CI coverage, automated checks, or test strategy related to Test on real mobile devices and viewports. Focus on whether the rule is continuously verified, not just documented. - 85integration-e2e-testing
Applies integration and E2E implementation, mock-boundary, and review rules. Use when: writing integration or E2E tests or reviewing their quality. - 100testing-strategy
Formulates a comprehensive testing strategy (Pyramid vs Trophy) and selects appropriate tools. Use when: test plan, testing strategy, qa strategy, e2e testing, integration testing, contract testing. - 100testing
Apply comprehensive testing best practices including unit, integration, and e2e tests. Use when writing tests, reviewing test coverage, designing testable code, or setting up test infrastructure. - 90fec-testing-strategy
Use when planning or reviewing a frontend testing strategy, selecting the right test layer by risk, mapping coverage across static checks, unit tests, component tests, integration tests, E2E, Storybook/visual regression, a11y, security, performance, or CI gates. Do not use to…