test-domain

Execute domain-scoped TypeScript tests and report concise results.

3|2|Updated Jun 25, 2024
One-click install
npx skills add https://github.com/Hopin-inc/civicship-api --skill test-domain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-domain
Source: https://github.com/Hopin-inc/civicship-api/tree/main/.claude/skills/test-domain
Command: npx skills add https://github.com/Hopin-inc/civicship-api --skill test-domain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly validate changes by running tests for a single domain, avoiding the slowness of full-suite test runs.

Core Features & Use Cases

  • Domain-scoped testing: Execute only the tests that belong to a specified domain (e.g., opportunity, user, wallet) to get fast feedback.
  • Focused reports: Generate concise results and coverage insights for the targeted domain.
  • Use Case: When making changes to the opportunity domain, run /test-domain opportunity to verify behavior without running unrelated tests.

Quick Start

Run a targeted domain test by specifying the domain name, e.g., /test-domain opportunity, to receive a fast, domain-scoped results report.

Frequently Asked Questions about test-domain

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

FAQPage Schema
How do I run tests for a single domain in TypeScript to get faster feedback?

Run domain-scoped tests by specifying the domain name, executing only matching test suites to provide fast feedback. It targets the specific domain to accelerate validation without running unrelated tests.

What is domain-scoped testing and when should I use it?

Domain-scoped testing executes only the tests belonging to a specific domain to provide quick validation. Use it when modifying a single domain to avoid the slowness of full-suite test runs.

How do I execute Jest tests for a specific domain like opportunity or user?

Execute Jest tests for a specific domain by applying the domain name to locate matching test patterns. It identifies and runs only the targeted domain's test suite to report concise results.

Does domain testing require a specific project structure to locate test files?

Domain testing requires access to TypeScript source under src/application/domain and test patterns in __tests__ to locate and run matching tests. It uses this structure to identify the correct domain test suite.

Can I get coverage insights for a targeted domain instead of the full project?

You can get coverage insights for a targeted domain by running domain-scoped tests. It generates concise results and coverage insights specifically for the targeted domain instead of the full project.

What are the limitations of running domain-focused tests instead of the full test suite?

Running domain-focused tests validates only the specified domain and does not execute unrelated tests. It accelerates feedback but might miss integration issues that a full test suite run would catch.