test-suite

Standardize TypeScript unit and integration tests with Jest, Vitest, and supertest.

Updated Nov 28, 2025
One-click install
npx skills add https://github.com/SoftSystemsStudio/Soft-Systems-Studio --skill test-suite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-suite
Source: https://github.com/SoftSystemsStudio/Soft-Systems-Studio/tree/main/.claude/skills/test-suite
Command: npx skills add https://github.com/SoftSystemsStudio/Soft-Systems-Studio --skill test-suite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Testing practices across teams can be inconsistent, leading to flaky tests, slow feedback, and duplicated effort. This Skill provides structured patterns, mock guidelines, and test organization conventions to streamline and improve reliability.

Core Features & Use Cases

  • Structured test patterns: Clear placement and naming for unit and integration tests across apps and packages.
  • Mock setup guidelines: Recommended order and approach for mocking dependencies before imports to ensure deterministic tests.
  • Harness and integration patterns: Reusable test harness examples and integration test patterns to speed up QA and regression testing.
  • Consistent organization: Standardized directories for tests to improve discoverability and collaboration.

Quick Start

Apply the test patterns to a new module or an existing one by placing unit tests in tests/ beside the implementation and integration tests under tests/integration/. Use the mock-before-import strategy shown in the examples to bootstrap tests quickly.

Frequently Asked Questions about test-suite

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize unit and integration tests in a TypeScript monorepo?

Standardize TypeScript test organization by placing unit tests in a __tests__/ directory beside the implementation and integration tests under tests/integration/. This convention improves discoverability and collaboration across apps and packages.

Why does my Jest test suite fail when mocking dependencies before imports?

Mock setup order is critical for deterministic TypeScript tests. Apply the mock-before-import strategy to bootstrap tests quickly, preventing flaky tests caused by incorrect initialization order and duplicated effort across your codebase.

Does this testing approach work with both Vitest and Jest?

Yes, this testing approach supports both Vitest and Jest. It standardizes TypeScript codebase testing by relying on both frameworks alongside supertest for HTTP tests to ensure repeatable, reliable results across your project.

What's the best way to structure HTTP integration tests for a TypeScript API?

Structure HTTP integration tests using supertest with reusable test harness patterns. This skill provides integration test patterns and harness examples under tests/integration/ to speed up QA and regression testing for TypeScript APIs.

How do I fix flaky tests caused by inconsistent mocking practices?

Fix flaky tests by applying structured mock setup guidelines that define the recommended order for mocking dependencies before imports. This ensures deterministic tests and eliminates unreliable results caused by inconsistent team testing practices.

Can I use these test patterns for an existing TypeScript codebase?

Yes, you can apply these test patterns to existing TypeScript codebases by placing unit tests in __tests__/ and integration tests in tests/integration/. The mock-before-import strategy allows you to bootstrap tests quickly for new or existing modules.