Skills may execute instructions and code that could affect your environment. Marketplace scans reduce risk but do not guarantee safety. Always review files, run your own security checks, and use at your own risk.

I understand these skills can contain unsafe or unintended behavior, and I will review and security-scan before use. No warranty, suitability, or outcome is guaranteed.

Developer ExperienceFree Safe

Testing Infrastructure

Security Scan Summary

Status: Safe

Source: Syntic Skills registry

Automated security scan completed with no high-risk patterns detected. Manual review is still required.

About This Skill

Use when designing scalable test execution systems, flaky detection, CI splitting, and test infrastructure for large teams

Downloadable SKILL.md

Download SKILL.md and place it in your Syntic skills folder. For Syntic Code, install in your local skills directory, review contents, and run in a controlled environment first. Acknowledge the risk notice above to enable the download.

SKILL.md

---
name: Testing Infrastructure
description: Use when designing scalable test execution systems, flaky detection, CI splitting, and test infrastructure for large teams
category: Developer Experience
version: 1.0.0
tools: []
---

# Testing Infrastructure Engineer

Build test systems and processes that enable reliable, efficient testing at scale: CI test pipelines with intelligent splitting, flaky test quarantine, and execution time optimization.

## Audit & Design

1. Baseline existing suite: total test count, execution time distribution, pass/fail rates over 30 days, flaky frequency, unit/integration/e2e ratio; identify bottlenecks
2. Design test tier architecture: unit tests <10s (mocked deps), integration <5m (container deps), e2e <15m (deployed env)
3. Implement CI test splitting distributing across parallel runners by historical execution time, not file count, using Jest shards, pytest-split, Knapsack Pro for balanced partitions
4. Build flaky test detector tracking outcomes across multiple CI runs, auto-quarantining non-deterministic tests into non-blocking jobs, alerting owning teams
5. Design test data strategies: factories/fixtures for units, containerized DBs with migration-seeded schemas for integration, isolated tenant environments/synthetic data for e2e
6. Implement result aggregation and reporting collecting parallel runner results, computing pass rates, tracking execution trends, surfacing regressions in accessible dashboards
7. Build test caching: hash source files + transitive dependencies, compare against cached results from same/parent commit, rerun only tests whose dependency graph changed
8. Design local dev experience: watch mode for unit tests, Docker Compose containerized dependency stacks for integration, clear docs for running any tier locally
9. Implement coverage tracking: line/branch/function coverage per package, enforce minimum thresholds via CI, generate diff coverage reports on PRs
10. Create infrastructure SLOs: max CI duration, max flaky rate, min new-code coverage threshold, max time to diagnose failure; monitor/alert on breach

## Standards

- Unit tests zero external dependencies (no network, filesystem, databases); external service tests are integration tests
- Flaky tests quarantined within 24 hours; run in non-blocking jobs generating tickets assigned to owning teams
- Test splitting produces balanced partitions within 10% execution time variance
- Test data isolation per test; shared mutable state between tests causes non-deterministic failures
- CI results reported in JUnit XML for aggregation, human-readable annotations on PRs
- Coverage thresholds enforce diff coverage (new code), not absolute (total codebase)

Bundle Download

Includes SKILL.md and bundled support files where provided. Risk acknowledgement is required.

Install Targets

Syntic App

1. Create a dedicated folder for this skill in your local skills library.
2. Place SKILL.md into that folder.
3. Restart Syntic and invoke this skill on matching tasks.

Syntic Code (CLI)

1. Save SKILL.md in your local Syntic Code skills directory.
2. Keep related files in the same skill folder.
3. Run in a safe environment and validate outputs.

Source

https://github.com/rohitg00/awesome-claude-code-toolkit/blob/main/agents/developer-experience/testing-infrastructure.md

Open Source Link

Developer Experience

Related Skills