How do I install the Aureuserp Test Case Builder skill?

Run npx skillmds@latest add aureuserp/aureuserp-test-case-builder in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Aureuserp Test Case Builder safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Aureuserp Test Case Builder?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Aureuserp Test Case Builder free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Aureuserp Test Case Builder?

aureuserp (@aureuserp) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Aureuserp Test Case Builder by aureuserp

Name: Aureuserp Test Case Builder
Author: aureuserp

Aureuserp Test Case Builder

Build and refactor Pest feature tests for AureusERP plugin APIs with reusable helpers, policy-permission auth setup, factory-first payloads, stable JSON assertions, and plugin-install bootstrap strategy. Use when creating or updating API tests under `plugins/*/*/tests`. This skill is structured to support a future Filament test-case track without changing current API behavior.

aureuserp c4f2a96 2 files · 4.2 KB Updated Sep 17, 2026

File contents

AureusERP Test Case Builder

Use this skill to build plugin API tests with Pest using test-only fixes and reusable helpers.

Scope Tracks

API test-case track (active now)

Follow references/api.md for end-to-end workflow, helper boundaries, assertions, and guardrails.

Filament test-case track (reserved for future)

Do not invent Filament-specific testing rules in this skill yet.
Keep API conventions unchanged.
When Filament guidance is added later, it should be added as separate references (for example references/filament-*.md) and selected explicitly by task type.

Core Rules

Use Pest feature tests for API endpoints (getJson, postJson, patchJson, deleteJson).
Prefer factories for setup and payload creation.
Keep helper responsibility split strict:

SecurityHelper for auth/permissions/guards.
TestBootstrapHelper for non-security bootstrap and plugin installation.

Do not use RefreshDatabase or LazilyRefreshDatabase in test files; use global DatabaseTransactions wiring.
Prefer test/helper fixes before app code edits.
Do not use skip-as-solution.

Quick Routing

API controller endpoint tests (index/store/show/update/destroy, auth, validation, restore/force-delete): use references/api.md.
API refactor/bugfix with helper cleanup: use references/api.md.
Template generation for a new plugin API test file: use references/api.md.

Output Expectations

Keep tests plugin-scoped and reusable.
Keep assertions deterministic and aligned with JSON resources.
Keep payloads factory-first with targeted overrides only.
Keep install/bootstrap non-interactive and environment-safe.

---name: aureuserp-test-case-builderdescription: Build and refactor Pest feature tests for AureusERP plugin APIs with reusable helpers, policy-permission auth setup, factory-first payloads, stable JSON assertions, and plugin-install bootstrap strategy. Use when creating or updating API tests under `plugins/*/*/tests`. This skill is structured to support a future Filament test-case track without changing current API behavior.---# AureusERP Test Case BuilderUse this skill to build plugin API tests with Pest using test-only fixes and reusable helpers.## Scope Tracks1. API test-case track (active now)- Follow `references/api.md` for end-to-end workflow, helper boundaries, assertions, and guardrails.2. Filament test-case track (reserved for future)- Do not invent Filament-specific testing rules in this skill yet.- Keep API conventions unchanged.- When Filament guidance is added later, it should be added as separate references (for example `references/filament-*.md`) and selected explicitly by task type.## Core Rules1. Use Pest feature tests for API endpoints (`getJson`, `postJson`, `patchJson`, `deleteJson`).2. Prefer factories for setup and payload creation.3. Keep helper responsibility split strict:- `SecurityHelper` for auth/permissions/guards.- `TestBootstrapHelper` for non-security bootstrap and plugin installation.4. Do not use `RefreshDatabase` or `LazilyRefreshDatabase` in test files; use global `DatabaseTransactions` wiring.5. Prefer test/helper fixes before app code edits.6. Do not use skip-as-solution.## Quick Routing1. API controller endpoint tests (`index/store/show/update/destroy`, auth, validation, restore/force-delete): use `references/api.md`.2. API refactor/bugfix with helper cleanup: use `references/api.md`.3. Template generation for a new plugin API test file: use `references/api.md`.## Output Expectations1. Keep tests plugin-scoped and reusable.2. Keep assertions deterministic and aligned with JSON resources.3. Keep payloads factory-first with targeted overrides only.4. Keep install/bootstrap non-interactive and environment-safe.

Frequently asked questions