test

Run yj-schema-validator tests with Maven Wrapper for full or targeted coverage.

4|Updated Sep 24, 2025
One-click install
npx skills add https://github.com/alexmond/yj-schema-validator --skill test-alexmond
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test
Source: https://github.com/alexmond/yj-schema-validator/tree/main/.claude/skills/test
Command: npx skills add https://github.com/alexmond/yj-schema-validator --skill test-alexmond

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run the yj-schema-validator test suite to verify code changes and ensure validator logic remains correct.

Core Features & Use Cases

  • Run all tests with a single command: ./mvnw test
  • Run targeted tests by class or method using -Dtest to focus on specific areas
  • Validate core validation logic, CLI runner, stdin handling, and output formatting through focused test suites

Quick Start

Run the full test suite with ./mvnw test, or target a specific class or method using -Dtest to verify changes.

Frequently Asked Questions about test

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

FAQPage Schema
How do I run unit tests for a Maven project using the Maven Wrapper?

Run unit tests for a Maven project using the Maven Wrapper by executing ./mvnw test, which automatically compiles the source code and executes the full test suite to verify code correctness.

Can I target a specific test class or method with Maven instead of running all tests?

Yes, you can target specific tests with Maven by using the -Dtest flag, allowing you to focus on individual classes or methods rather than executing the entire suite.

Do I need a system Maven installation to run integration tests locally?

No, you do not need a system Maven installation to run integration tests. The workflow relies on the Maven Wrapper (./mvnw), which downloads and uses the correct Maven version automatically.

What is the best way to validate changes to CLI runner and stdin handling logic?

The best way to validate changes to CLI runner and stdin handling logic is to execute targeted unit and integration tests using ./mvnw test -Dtest to isolate and verify the specific modified components.

Why does my Maven test command fail to execute the full validation test suite?

Your Maven test command might fail if the Maven Wrapper is missing or if the project lacks the required test files, preventing the validator logic and output formatting tests from executing correctly.