- What is richcongress/test-framework used for?
- It is a Composer package that provides a structured testing framework for PHP and Laravel application test suites. Its overview highlights a PHPUnit extension with priorities, intended to simplify test organization and common testing workflows. It is aimed at developers who want more consistency in how tests are written and maintained.
- How do I install richcongress/test-framework in a Laravel project?
- Install it with Composer using composer require richcongress/test-framework. Because it is a testing tool, you will typically add it as a development dependency with the --dev flag. After installation, follow the package's PHPUnit extension setup instructions so the framework is loaded during test runs.
- Does richcongress/test-framework work with PHPUnit's extension system?
- Yes, the package description states that it uses the PHPUnit Extension with priorities. That means it is designed to integrate into PHPUnit's extension mechanism rather than replace PHPUnit itself. You should confirm the exact extension class and registration syntax in the package documentation for your PHPUnit version.
- How do test priorities work in richcongress/test-framework?
- The package is described as a PHPUnit extension with priorities, which suggests it supports ordering or prioritizing tests within a suite. The provided overview does not document the exact priority syntax or behavior. Check the package's README or source for how priorities are declared and how they affect test execution.
- Which Laravel and PHP versions are supported?
- The available context does not specify supported Laravel or PHP versions. You should check the package's composer.json on Packagist for PHP, PHPUnit, and Laravel version constraints before installing. Matching those constraints to your application's Laravel version is important for compatibility.
- How do I configure richcongress/test-framework in phpunit.xml?
- Because it is a PHPUnit extension, configuration is likely handled through PHPUnit's extension registration rather than a Laravel config file. The exact phpunit.xml snippet depends on the PHPUnit version and the extension class provided by the package. Consult the package README for the correct extension entry and any priority-related options.
- Should richcongress/test-framework be a dev dependency?
- Yes, testing frameworks are normally required only for development and CI, so install it with composer require --dev richcongress/test-framework. Keeping it in require-dev prevents test-only code from being installed in production. Verify this against the package's own installation instructions.
- Can I use richcongress/test-framework in CI/CD pipelines?
- It can be used in CI/CD where your Laravel test suite runs, provided your pipeline installs dev dependencies and uses a compatible PHP and PHPUnit version. Since it extends PHPUnit, your existing test commands should continue to work once the extension is registered. Check the package docs for any CI-specific setup or priority ordering concerns.
- What alternatives exist to richcongress/test-framework for Laravel testing?
- Laravel's default testing stack is built on PHPUnit and Pest, and both are widely used alternatives for organizing Laravel test suites. If you only need test ordering, PHPUnit's own features and test suite configuration may be sufficient. Evaluate richcongress/test-framework specifically for its priority-based PHPUnit extension behavior.
- Is richcongress/test-framework actively maintained?
- The provided context does not include release history, repository activity, or maintenance status. Before adopting it, check Packagist and the repository for recent releases, open issues, and compatibility with current Laravel and PHPUnit versions. Maintenance activity is an important factor for a package that integrates deeply with your test suite.