Download the PHP package srlabs/laravel-testing-utilities without Composer
On this page you can find all versions of the php package srlabs/laravel-testing-utilities. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package laravel-testing-utilities
Laravel Utilities
This package is intended to be a collection of helpful utilities to assist with the development and maintenance of Laravel Applications.
| Laravel Version | Package Version | Packagist Branch |
|---|---|---|
| 7.* | 10.* | |
| 8.* | 11.* | |
| 9.* | 12.* |
To install this package, run
and then add the service provider to your service providers listing in
Testing Assistant
This utility makes it easy to implement the testing stratgey described by Chris Duell in his blog post Speeding up PHP unit tests 15 times. When running tests that require the use of a database persistence layer, running migrations and seeding the database for each test can take a very long time. Chris instead suggests creating a sqlite database file ahead of time, and making a new copy of that file for each test instead.
This package provides an artisan command ('utility:testdb') that will run your migrations and seeds and save them to a pre-defined sqlite file. Once that is complete, there is a companion trait that you add to your tests which will copy the staging database file to the testing database location when running tests.
You need to define a sqlite database connection in your file. The connection name can be whatever you would like, but the package will assume a name of 'staging' if you don't provide one.
Default 'staging' connection:
Custom 'sqlite_testing' connection:
You can also specify a Database Seeder class:
This command will migrate and seed the sqlite database you have specified.
When you are ready to use this new sqlite file in your tests, add the trait to your test class, and use it as such:
In this example "staging" is the Database connection that represents the pre-compiled sqlite file, and "testing" is a separate connection that represents the database that will be used by the tests. Each time the method is called, the testing sqlite file will be replaced by the staging sqlite file, effectively resetting your database to a clean starting point. You may need to do some extra configuration to have phpunit use your "testing" database.
(Optional) Run Automatically When Running PHPUnit
Using this method will have artisan utility:testdb execute before any tests are ran only if there are new migration changes.
1. Create file bootstrap/testing.php:
2. Update phpunit.xml
All versions of laravel-testing-utilities with dependencies
illuminate/support Version ^9.0
illuminate/contracts Version ^9.0
illuminate/database Version ^9.0