# Bagisto Pest Testing

> Use when writing or changing a Bagisto Pest test — feature or unit tests, assertions, datasets, mocking, architecture tests, or registering a new package's suite. Trigger phrases include "pest", "test", "unit test", "feature test", "assertion", "dataset", "mock", "testsuite", "TDD", "coverage".

- Skill: `bagisto/bagisto-pest-testing` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add bagisto/bagisto-pest-testing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bagisto/bagisto-pest-testing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- License: MIT
- Author: bagisto (https://skillmd.com/u/bagisto)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/bagisto/bagisto-pest-testing

---


# Pest Testing in Bagisto

## When to Apply

Activate this skill when:
- Creating new tests (unit or feature)
- Modifying existing tests
- Debugging test failures
- Working with datasets, mocking, or test organization
- Writing architecture tests
- Testing Bagisto packages (Admin, Shop, Core, etc.)

## Reference files — load only what the current task needs

| File | Load when |
|---|---|
| [suite-layout.md](suite-layout.md) | Where tests live, the suites, Pest.php bindings, autoload wiring |
| [writing-tests.md](writing-tests.md) | Running tests, test structure, assertions, mocking, datasets, architecture tests |
| [new-package.md](new-package.md) | Registering a new package's tests, pitfalls, best practices |

**REQUIRED SUB-SKILL:** Use bagisto-change-verification before calling any change done.