Integration Test Setup - Auto-activating skill for Test Automation. Triggers on: integration test setup, integration test setup Part of the Test Automation skill category.
36
Quality
7%
Does it follow best practices?
Impact
86%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/09-test-automation/integration-test-setup/SKILL.mdJest integration test setup for Node.js
Jest framework used
100%
100%
Jest config file present
100%
100%
Integration test environment config
100%
100%
Test file naming convention
100%
100%
At least one integration test written
100%
100%
Test script in package.json
100%
100%
Coverage configuration
0%
0%
Mocking setup present
16%
0%
Setup/teardown lifecycle hooks
100%
100%
No forbidden frameworks
100%
100%
Without context: $0.4704 · 2m 21s · 25 turns · 26 in / 7,167 out tokens
With context: $0.6218 · 2m 17s · 35 turns · 34 in / 7,973 out tokens
Pytest integration test setup for Python
Pytest framework used
100%
100%
Pytest config file present
100%
100%
conftest.py with fixtures
100%
100%
Integration test file present
100%
100%
Test dependencies documented
100%
100%
Mocking setup present
0%
0%
Fixture scope used
100%
100%
Coverage configuration
0%
0%
Test isolation ensured
100%
100%
No forbidden frameworks
100%
100%
Without context: $0.6313 · 2m 23s · 33 turns · 34 in / 8,894 out tokens
With context: $0.7424 · 2m 20s · 39 turns · 40 in / 8,468 out tokens
Mocking external dependencies in integration tests
Mocking library referenced
100%
100%
External service mocked
100%
100%
Mock defined before test runs
100%
100%
Mock reset or cleanup
100%
100%
Production-ready config
80%
90%
Test verifies mock was called
100%
100%
Framework-consistent mocking
100%
100%
At least one integration test
100%
100%
Step-by-step README
100%
100%
Without context: $0.6646 · 2m 47s · 31 turns · 32 in / 9,868 out tokens
With context: $0.7657 · 2m 37s · 39 turns · 1,466 in / 9,542 out tokens
f17dd51
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.