test-integration
/test-integration
Test how components work together. Test database + API, auth + user service, etc. Use when testing multi-component flows or after unit tests pass.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 22.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
Test how components work together. Test database + API, auth + user service, etc. Use when testing multi-component flows or after unit tests pass.
Original author description
Test how components work together. Test database + API, auth + user service, etc. Use when testing multi-component flows or after unit tests pass.
How it works
- When To Use
- What To Test
- Output
SKILL.md preview
---
name: test-integration
description: Test how components work together. Test database + API, auth + user service, etc. Use when testing multi-component flows or after unit tests pass.
license: MIT
metadata:
author: vant
version: "1.0"
---
# Integration Test
> Components working together.
## When To Use
- Multi-component flows
- After unit tests pass
- Before e2e tests
## What To Test
### 1. Database + API
```javascript
test('user created in DB', async () => {
const user = await userService.create({ email: 'test@example.com' })
const inDb = await db.users.find(user.id)
expect(inDb).toEqual(user)
})
```
### 2. Auth + User Service
```javascript
test('login returns user', async () => {
const session = await auth.login('test@example.com', 'password')
expect(session.user.email).toBe('test@example.com')
})
```
### 3. Queue + Worker
```javascript
test('job processed', async () => {
const job = await queue.add({ task: 'process' })
await worker.process(job.id)
expect(job.status).toBe('complete')
})
```
---
## Output
```
## Integration Tests
| Flow | Status |
|------|--------|
| DB + API | [PASS/FAIL] |
| Auth + User | [PASS/FAIL] |
| Queue + Worker | [PASS/FAIL] |
### Time
[n] seconds
```
**Role**: Integration Tester
**Input**: Components
**Output**: Integration results
Versions
The database has no other skills named test-integration.
Database snapshot: 13.11.2026 · package version 6791cea5cf8a (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
- 100qa-integration-testing
Creates integration tests that verify interactions between application components, databases, APIs, and external services. Use when testing real component integrations in a controlled test environment. Not for isolated unit testing (use qa-unit-testing). - 95integration-test-writer
Generate comprehensive integration tests for component interactions, workflows, and system boundaries. Use for testing API endpoints, database operations, and multi-component flows. - 100integration-testing
Integration testing patterns for database state, API contracts, service boundaries, and component wiring. Use when testing how multiple parts of a system work together without mocks. - 90quality-integration-testing
Use when the user asks about integration testing, component testing, API testing, database testing, test containers, wiremock, contract testing, or service-level testing. Do NOT use for: unit testing (quality-unit-testing), E2E testing (quality-e2e-testing), or 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. - 100writing-tests
Use when writing, reviewing, or refactoring any automated test — unit, component, or integration — including whenever a test file (*.test.*, *.spec.*) or a component test is authored or changed.