test-frontend

Run frontend test suites and filtered test executions using project-defined commands.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly run frontend tests without hunting for the right project-specific command or remembering how to filter test execution.

Core Features & Use Cases

  • Run all frontend tests: Executes the standard frontend test command defined by the repository's technology conventions.
  • Run targeted tests: Supports passing a test filter argument for narrower test runs, such as a feature, API, or logic area.
  • Use Case: When updating authentication or registration flows, you can run only the related frontend tests to validate changes faster and reduce feedback time.

Quick Start

Ask to use the test-frontend skill to run all frontend tests or to run a filtered frontend test for a specific feature name.

Frequently Asked Questions about test-frontend

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

FAQPage Schema
How do I run frontend tests for a specific feature without executing the entire suite?▼

You can run filtered frontend tests by passing a specific feature name or test filter argument, executing only the relevant test cases instead of the entire suite.

How does this approach find the correct vitest commands for my repository?▼

It reads the frontend testing convention from ProductSpecification/technology.md to execute the project-defined test commands and report the resulting test output.

Can I use this to validate UI behavior and frontend API integration?▼

Yes, it applies to scenarios where you need to validate UI behavior, feature-specific logic, or frontend API integration through project-defined test commands.

What is the best way to execute all frontend tests defined in my project?▼

The best way is to execute the standard frontend test command defined by the repository's technology conventions, running the full test suite and reporting the output.

Do I need a specific test runner like vitest configured to use this?▼

You need the frontend testing convention specified in ProductSpecification/technology.md, as the Skill reads this file to execute the project-defined test runner and commands.