Weave Code
Test Support Laravel Package
tipoff/test-support
Deprecated/archived package providing shared unit/feature testing support for Tipoff Laravel packages. Previously included common test utilities and configuration; being removed as a dependency so packages can update independently and adopt newer Laravel versions faster.
PHP Package for test support on other packages
Frequently asked questions about Test Support
- Does tipoff/test-support fix Blade template test failures specifically on Windows in Laravel?
- Yes, the package includes a Laravel-specific fix (v2.0.1) for Blade template testing on Windows, addressing path/resolution issues that cause silent failures in CI/CD pipelines. It’s targeted at resolving cross-platform Blade compilation inconsistencies.
- Can I use this package with Laravel 10 or PHP 8.1+?
- The package likely supports modern Laravel versions due to its Blade compiler fix, but there’s no explicit PHP 8.1+ declaration. Test compatibility by running your Blade tests on both Windows and Linux/macOS runners to confirm no regressions.
- Will this package conflict with PestPHP or PHPUnit?
- No, the package is framework-agnostic and doesn’t impose dependencies on PestPHP or PHPUnit. It focuses solely on Blade template testing utilities, so it integrates seamlessly with either testing framework.
- Is this package still maintained? Should I use it in production?
- The package is deprecated and archived, with no updates since 2021. Use it cautiously for Blade-specific fixes, but plan for a fork or replacement if maintenance stalls. It’s safe for testing but not for production-critical dependencies.
- How do I install tipoff/test-support for Laravel Blade testing?
- Run `composer require tipoff/test-support --dev` to install it as a development dependency. The package doesn’t require additional configuration—just ensure your Blade tests target the fixed path/resolution logic.
- Does this package support custom Blade directives or non-standard template paths?
- The package’s Windows Blade fix assumes default Laravel Blade cache paths (storage/framework/views). If your project uses custom directives or non-standard paths, validate compatibility by testing edge cases in your CI pipeline.
- Can I use this for HTTP/API testing in Laravel?
- No, this package is Blade-focused and doesn’t include utilities for HTTP/API testing. For those needs, use Laravel’s built-in HttpTests or PestPHP’s HTTP client features instead.
- Will this package break if I use Laravel’s Blade cache in a custom location?
- Potentially. The fix may rely on Laravel’s default Blade cache paths. If you’ve customized the cache location, test thoroughly or mock the FileViewFinder to avoid conflicts.
- Are there alternatives to tipoff/test-support for Blade testing?
- For Blade-specific issues, consider Laravel’s native testing tools or PestPHP’s Blade helpers. If you need Windows-specific fixes, check for community forks or extract the Blade logic into your own test utilities.
- How do I migrate away from this package if it’s deprecated?
- Start by isolating Blade-related tests to use the package’s utilities. Gradually replace its dependencies with Laravel’s built-in features or modern alternatives like PestPHP. Test incrementally to avoid regressions.
Weaver
How can I help you explore Laravel packages today?