test-usecase

Run backend use-case tests using the repository's test command convention.

2|1|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/is-ivanov/rpm-ddd --skill test-usecase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-usecase
Source: https://github.com/is-ivanov/rpm-ddd/tree/main/.opencode/skills/test-usecase
Command: npx skills add https://github.com/is-ivanov/rpm-ddd --skill test-usecase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly run backend use-case tests without manually figuring out the correct project-specific test command pattern.

Core Features & Use Cases

  • Fast test execution: Runs all use-case module tests when you want broad verification.
  • Targeted filtering: Supports running only tests that match a provided filter for faster debugging.
  • Project-aware workflow: Uses the backend test command convention defined in the repository's technology documentation.
  • Use Case: When a developer changes application-layer logic and wants immediate feedback, this Skill can run only the relevant use-case tests instead of the full test suite.

Quick Start

Ask the AI to run the test-usecase skill for all use-case tests or provide a test name filter to narrow the run.

Frequently Asked Questions about test-usecase

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

FAQPage Schema
How do I run a filtered subset of backend use-case tests for faster debugging?

You can run a filtered subset of backend use-case tests by providing a test name filter to the skill, which applies the repository's defined test command convention to execute only matching tests for immediate feedback.

How does the backend use-case test execution mechanism resolve the correct command pattern?

The test execution mechanism resolves the correct command pattern by reading the ProductSpecification/technology.md file in the repository to find and apply the project's defined backend test command convention.

Do I need a specific testing framework configured to run backend use-case tests?

You do not need a specific framework configured beyond the project's existing setup, as the skill uses the backend test command convention already defined in the repository's technology documentation.

What is the best way to execute all backend use-case tests after changing application-layer logic?

The best way to execute all backend use-case tests is to invoke the skill without a filter, running the full test suite using the project-specific test command pattern for broad verification.

Why should I use filtered use-case testing instead of running the full test suite?

You should use filtered use-case testing to get immediate, targeted feedback on application-layer logic changes without waiting for the full test suite to complete, significantly speeding up development and debugging.

Can test-usecase run my Maven backend tests automatically?

test-usecase runs your Maven backend tests by resolving the test command pattern from the repository's technology documentation and executing the specified test command convention automatically.