test-helpers

Generate engine-specific test helper libraries under tests/helpers/.

Updated Feb 8, 2024
One-click install
npx skills add https://github.com/kay6198835/Game-RPG --skill test-helpers-kay6198835
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-helpers
Source: https://github.com/kay6198835/Game-RPG/tree/main/.claude/skills/test-helpers
Command: npx skills add https://github.com/kay6198835/Game-RPG --skill test-helpers-kay6198835

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate engine-specific test helper libraries for the project's test suite. Reads existing test patterns and produces tests/helpers/ with assertion utilities, factory functions, and mock objects tailored to the project's systems. Reduces boilerplate in new test files.

Core Features & Use Cases

  • Generate a tests/helpers/ library tailored to the project's engine, language, and systems to reduce boilerplate and increase consistency.
  • Provide assert utilities, factory functions, and mock objects for common test scenarios.
  • Integrate with existing test patterns by reading a subset of files and configuring outputs to match the project's style.

Quick Start

Invoke the test-helpers skill for a target system or all systems to generate engine-aligned test helpers in tests/helpers/.

Frequently Asked Questions about test-helpers

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

FAQPage Schema
How do I generate mock objects and factory functions to reduce unit test boilerplate?

Generate engine-specific test helper libraries by reading existing test patterns and producing deterministic files under tests/helpers/ with assertion utilities, factory functions, and mock objects to reduce boilerplate. It detects the engine and language from configuration to tailor outputs.

Does test-helpers overwrite existing helper files when generating engine-specific test utilities?

No, test-helpers generates deterministic helper files under tests/helpers/ without overwriting existing ones. It parses a subset of existing test files to configure outputs that match the project style and patterns.

What's the best way to create consistent unit test setup across multiple engines?

Invoke test-helpers for a target system or all systems to generate engine-aligned test helpers in tests/helpers/. It detects engine and language from configuration to ensure consistent assertion utilities and mock objects across all project test suites.

Can I use test-helpers with GDD-driven test coverage and existing test patterns?

Yes, test-helpers integrates with existing test patterns and GDD-driven test coverage. It reads a subset of files to configure outputs that match the project style, generating tailored assert utilities, factory functions, and mock objects.

How do test helper libraries integrate with my project's current test automation setup?

Test helper libraries integrate by reading existing test patterns from a subset of files and configuring outputs to match the project style. This ensures the generated assertion utilities and mock objects align with current test automation engines and languages.

Why do I need engine detection when generating unit test helpers?

Engine detection is needed to generate engine-specific test helpers tailored to the project's language and systems. It ensures the produced assertion utilities, factory functions, and mock objects match the correct test automation framework configuration.