Weave Code
Code Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Phpspec Skip Example Extension Laravel Package

graham-campbell/phpspec-skip-example-extension

PhpSpec extension that lets you skip spec examples via simple annotations. Add @require ClassOrInterface to skip all examples in a spec when a dependency isn’t available. Install with Composer and enable in phpspec.yml.

View on GitHub
Deep Wiki
Context7

Technical Evaluation

This package is irrelevant for standard Laravel projects as it targets PhpSpec, a BDD testing framework not natively supported by Laravel. Laravel's default testing stack uses PHPUnit exclusively, with no industry adoption of PhpSpec in Laravel ecosystems. The package has zero dependents, last updated in 2021, and low community engagement (0 stars), indicating abandonment. Technical risks include potential incompatibility with modern PhpSpec versions and zero maintenance guarantees. Key questions: Does our project use PhpSpec? (Almost certainly no). Are there Laravel-native alternatives for conditional test skipping? (Yes - PHPUnit's @requires or environment-based skips). Why would we introduce an unsupported testing framework?

Integration Approach

Stack fit is fundamentally incompatible - Laravel's test infrastructure (PHPUnit, Pest) has no integration points for PhpSpec extensions. Migration path would require replacing Laravel's entire testing stack with PhpSpec, which is commercially unsupported and contradicts Laravel's official documentation. Compatibility is nonexistent for current Laravel versions (8+), as PhpSpec isn't part of the framework's dependency tree. Sequencing would be impossible without first abandoning Laravel's testing conventions entirely, which would create massive technical debt and break all existing test suites.

Operational Impact

Maintenance burden would be extreme due to zero active maintainers and no recent updates. Support would rely on community forums with no guaranteed response time (0 dependents = no user base). Scaling would be irrelevant since the package isn't applicable, but if forced into use, test failures would cascade unpredictably due to outdated code. Ramp-up would require training developers on PhpSpec - a framework Laravel never adopted - creating unnecessary cognitive load. Failure modes include silent test skipping errors, broken CI pipelines, and wasted engineering time debugging an unsupported tool.

Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
davejamesmiller/laravel-breadcrumbs
artisanry/parsedown
christhompsontldr/phpsdk
enqueue/dsn
bunny/bunny
enqueue/test
enqueue/null
enqueue/amqp-tools
milesj/emojibase
bower-asset/punycode
bower-asset/inputmask
bower-asset/jquery
bower-asset/yii2-pjax
laravel/nova
spatie/laravel-mailcoach
spatie/laravel-superseeder
laravel/liferaft
nst/json-test-suite
danielmiessler/sec-lists
jackalope/jackalope-transport