一键在 Manus 中运行任何 Skill

package-testing

星标69

分支1

更新时间2026年4月29日 12:47

Use this skill when writing, editing, fixing, or reviewing package tests with Pest 4 and Orchestra Testbench, including TDD, feature tests, unit tests, type coverage, arch tests, workbench behavior, commands, routes, config, migrations, and publishable resources.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

WendellAdriel

WendellAdriel/laravel-expressive

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Package Testing

Primary Goal

Prove package behavior with Pest 4, Orchestra Testbench, and the local tests/TestCase.php setup before or alongside implementation.

Workflow

Start with TDD: write the smallest failing package test for the requested behavior, then implement the smallest change that makes it pass.
Cover happy-path, unhappy-path, and edge-case behavior when the feature has meaningful failure modes.
Prefer focused feature tests for package integration behavior and arch tests for broad constraints.
Use composer test:unit -- --filter ... while iterating, composer test:types when type-sensitive tests or code changed, and composer test before finishing.
Keep real package tests in the suite and remove only throwaway tests that were explicitly created for local scaffolding experiments.

References

tests/TestCase.php
tests/Pest.php
tests/Feature/
tests/Unit/
tests/ArchTest.php
composer.json scripts

Examples

Test config merge and config override by asserting default package config, then overriding the host config value in the Testbench app.
Test publishable assets, migrations, views, lang files, or config by invoking vendor publish behavior and asserting the target path exists.
Test routes with Testbench HTTP requests, commands with Artisan assertions, migrations with a SQLite test database, and workbench behavior after composer build when needed.

Anti-Patterns

Deleting real package tests because they are inconvenient.
Relying only on smoke tests when behavior needs assertions.
Testing implementation details when observable package behavior is available.
Keeping throwaway scaffolding experiment tests in the package test suite.

同仓库更多 Skills

同仓库

expressive-development

WendellAdriel/laravel-expressive

Integrate and use `wendelladriel/laravel-expressive` in Laravel applications. Use this when installing Expressive, configuring class lookup, creating typed Expressive objects, converting Eloquent models or collections, generating or syncing Expressive classes, serializing objects, or persisting Expressive objects back through Eloquent.

2026-07-0369

package-release

WendellAdriel/laravel-expressive

Use this skill when preparing Laravel package releases: generated release notes, GitHub release workflows, version checks, tags, release validation, or release automation changes. Never publish autonomously.

2026-06-0869

package-docs

WendellAdriel/laravel-expressive

Use this skill when writing or revising package documentation after creating a package from this starter: README content, VitePress pages, contributing docs, upgrade notes, installation, usage, testing, workbench docs, or examples.

2026-05-2769

package-generate-skill

WendellAdriel/laravel-expressive

Use this skill when creating or updating the bundled Laravel Boost skill under resources/boost/skills from the package implementation and documentation. Trigger after public APIs, commands, config, routes, views, publish tags, examples, or docs change.

2026-05-2669

package-scaffold

WendellAdriel/laravel-expressive

Use this skill when adding Laravel package capabilities or package shape changes after creating a package from this starter: commands, migrations, routes, config, views, assets, middleware, workbench files, or new publishable resources.

2026-04-3069

package-service-provider

WendellAdriel/laravel-expressive

Use this skill when changing a Laravel package service provider: config merges, routes, views, translations, publishing, migrations, assets, Blade components, commands, console-only behavior, or package metadata.

2026-04-3069

name	package-testing
description	Use this skill when writing, editing, fixing, or reviewing package tests with Pest 4 and Orchestra Testbench, including TDD, feature tests, unit tests, type coverage, arch tests, workbench behavior, commands, routes, config, migrations, and publishable resources.
license	MIT
metadata	{"author":"laravel"}

Package Testing

Primary Goal

Prove package behavior with Pest 4, Orchestra Testbench, and the local tests/TestCase.php setup before or alongside implementation.

Workflow

Start with TDD: write the smallest failing package test for the requested behavior, then implement the smallest change that makes it pass.
Cover happy-path, unhappy-path, and edge-case behavior when the feature has meaningful failure modes.
Prefer focused feature tests for package integration behavior and arch tests for broad constraints.
Use composer test:unit -- --filter ... while iterating, composer test:types when type-sensitive tests or code changed, and composer test before finishing.
Keep real package tests in the suite and remove only throwaway tests that were explicitly created for local scaffolding experiments.

References

tests/TestCase.php
tests/Pest.php
tests/Feature/
tests/Unit/
tests/ArchTest.php
composer.json scripts

Examples

Test config merge and config override by asserting default package config, then overriding the host config value in the Testbench app.
Test publishable assets, migrations, views, lang files, or config by invoking vendor publish behavior and asserting the target path exists.
Test routes with Testbench HTTP requests, commands with Artisan assertions, migrations with a SQLite test database, and workbench behavior after composer build when needed.

Anti-Patterns

Deleting real package tests because they are inconvenient.
Relying only on smoke tests when behavior needs assertions.
Testing implementation details when observable package behavior is available.
Keeping throwaway scaffolding experiment tests in the package test suite.