Name: Quarkus Test Guidelines
Author: navarrorncf

Instruction file imported from navarrorncf/habit-tracker (.github/instructions/quarkus-tests.instructions.md). Copyright stays with the author.

Quarkus Test Guidelines

Use @QuarkusTest for fast tests that exercise the application in the test runtime.
Use @QuarkusIntegrationTest for tests that must exercise the packaged application. Keep the distinction explicit in the test name and summary.
Use REST Assured for HTTP behavior and assert status codes and meaningful response content, not only that a request completes.
Keep tests deterministic and isolated. Do not add sleeps, calls to personal services, or reliance on an undeclared local process.
Follow nearby naming, fixture, and setup patterns. Add the smallest fixture needed to make the behavior clear.
Test boundary cases and failure behavior when the change introduces them.
Run ./mvnw test for the fast feedback loop, then ./mvnw verify -B before considering the change complete.
If a test requires PostgreSQL or another external service that is not configured in the repository, state that limitation instead of silently weakening the test.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install Quarkus Test Guidelines and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "navarrorncf-habit-tracker-quarkus-tests-instructions", "kind": "skill", "name": "Quarkus Test Guidelines", "description": "Use when creating or modifying Quarkus tests, REST Assured tests, integration tests, test fixtures, or Maven test configuration.", "publisher": "navarrorncf", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github-instructions" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Use when creating or modifying Quarkus tests, REST Assured tests, integration tests, test fixtures, or Maven test configuration." ], "primary": false, "metadata": { "source": { "provider": "github-instructions", "repository": "https://github.com/navarrorncf/habit-tracker", "path": ".github/instructions/quarkus-tests.instructions.md", "ref": "b0d30d0d468d8512d694c219722254d1908f99a6", "url": "https://github.com/navarrorncf/habit-tracker/blob/b0d30d0d468d8512d694c219722254d1908f99a6/.github/instructions/quarkus-tests.instructions.md", "key": "navarrorncf/habit-tracker/.github/instructions/quarkus-tests.instructions.md" }, "applies_to": "src/test/**/*.java" }, "instructions": "# Quarkus Test Guidelines\n\n- Use `@QuarkusTest` for fast tests that exercise the application in the test\n runtime.\n- Use `@QuarkusIntegrationTest` for tests that must exercise the packaged\n application. Keep the distinction explicit in the test name and summary.\n- Use REST Assured for HTTP behavior and assert status codes and meaningful\n response content, not only that a request completes.\n- Keep tests deterministic and isolated. Do not add sleeps, calls to personal\n services, or reliance on an undeclared local process.\n- Follow nearby naming, fixture, and setup patterns. Add the smallest ", "cost": { "context_tokens": 250 } }

Quarkus Test Guidelines

About

Quarkus Test Guidelines

Use it

Install Quarkus Test Guidelines and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews