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.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "aureuserp-test-case-builder" with this command: npx skills add aureuserp/agent-skills/aureuserp-agent-skills-aureuserp-test-case-builder

AureusERP Test Case Builder

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

Scope Tracks

  1. API test-case track (active now)
  • Follow references/api.md for end-to-end workflow, helper boundaries, assertions, and guardrails.
  1. 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

  1. 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.
  1. Do not use RefreshDatabase or LazilyRefreshDatabase in test files; use global DatabaseTransactions wiring.
  2. Prefer test/helper fixes before app code edits.
  3. Do not use skip-as-solution.

Quick Routing

  1. 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 Expectations

  1. 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.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Open in GitHubOpen in ClawHub

Related Skills

Related by shared tags or category signals.

Automation

aureuserp-api-builder

No summary provided by upstream source.

Repository SourceNeeds Review
6-aureuserp
Automation

aureuserp-plugin-builder

No summary provided by upstream source.

Repository SourceNeeds Review
6-aureuserp
Automation

vercel-composition-patterns

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

Repository Source
86.4K23Kvercel
Automation

vercel-react-native-skills

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

Repository Source
60.7K23Kvercel