testing-patterns

Generate QUAIL-compliant antenna designs from plain-English descriptions.

1|1|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/emvnuel/SKILL.md --skill testing-patterns-emvnuel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-patterns
Source: https://github.com/emvnuel/SKILL.md/tree/main/testing-patterns
Command: npx skills add https://github.com/emvnuel/SKILL.md --skill testing-patterns-emvnuel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes REST integration testing patterns to help teams verify endpoint behavior reliably and repeatedly, reducing fragile tests and ad-hoc approaches.

Core Features & Use Cases

  • REST Integration Tests: end-to-end validation of HTTP endpoints using Quarkus @QuarkusTest and RestAssured.
  • Mocking External Dependencies: isolate tests from external services with Mockito-based mocks and CDI integration.
  • Database Patterns: testcontainers for real database behavior and H2 for fast local iterations.
  • Raw JSON Payloads: validate exact request bodies using text blocks and JSON path assertions.
  • Cookbook & Patterns: guided recipes and best practices to organize and reuse test patterns.

Quick Start

Start by creating a Quarkus test class, add representative tests, and run your test suite with mvn test or mvn -Dtest=YourTestClass test. Adapt patterns to your application endpoints.

Frequently Asked Questions about testing-patterns

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

FAQPage Schema
How do I write repeatable REST integration tests for Quarkus endpoints?

Repeatable REST integration tests for Quarkus endpoints are built using @QuarkusTest and RestAssured to validate HTTP behavior end-to-end. This standardizes test patterns and reduces ad-hoc approaches. The Skill provides cookbook recipes to organize and reuse these tests.

What's the best way to isolate external dependencies during Java integration testing?

Isolating external dependencies during Java integration testing is handled with Mockito-based mocks and CDI integration. This separates tests from external services, ensuring endpoint behavior is verified reliably without live network calls or fragile external service dependencies.

Can I use Testcontainers and H2 for database integration tests in JUnit 5?

Testcontainers and H2 can be used for database integration tests in JUnit 5 to verify database patterns. Testcontainers provides real database behavior, while H2 enables fast local iterations, covering both realistic testing and rapid development cycles.

How do I validate raw JSON payloads using RestAssured and text blocks?

Raw JSON payloads are validated using RestAssured and Java text blocks to define exact request bodies. JSON path assertions are then applied to verify the response structure and values, ensuring precise payload testing without manual string concatenation.

Does this approach support structured test patterns for Java services beyond basic unit tests?

Structured test patterns for Java services are fully supported, covering endpoint behavior, dependency isolation, and database integration. It applies JUnit 5, Mockito, and RestAssured to provide clear cookbook references that go beyond basic unit tests.

Why are my REST integration tests fragile and how can I standardize them?

Fragile REST integration tests often stem from ad-hoc approaches and lack of repeatable patterns. Standardizing them with Quarkus, RestAssured, and Testcontainers ensures reliable endpoint verification, dependency isolation, and consistent database integration.