Download the PHP package tonysm/laravel-paratest without Composer
On this page you can find all versions of the php package tonysm/laravel-paratest. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download tonysm/laravel-paratest
More information about tonysm/laravel-paratest
Files in tonysm/laravel-paratest
Package laravel-paratest
Short Description Run your Laravel feature tests in parallel without race conditions.
License MIT
Homepage https://github.com/tonysm/laravel-paratest
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-paratest
Parallel Integration Tests in Laravel
This package ships with some helper Artisan commands and testing traits to allow you running your Feature Tests in parallel using Paratest against a MySQL or PostgreSQL database without conflicts.
The package will create 1 database for each testing process you have running to avoid race conditions when your Feature Test try to run a test creating some fixtures while another test in a another process runs the artisan migrate:fresh.
You also don't have to worry about creating the test databases. They will be created when you run your tests. There's is even a helper runner to clean up the test databases afterwards.
Installation
You can install the package via composer:
Usage
Attention: You will need a user with rights to create databases.
Instead of using Laravel's RefreshDatabase trait, use the package one:
Tip: to replace all existing usages of Laravel's RefreshDatabase trait with the package's, you can use the following command:
You need to boot this setup trait in your base TestCase manually, because Laravel does not do it automatically:
You can keep running you tests with PHPUnit:
Or you can use Paratest:
When using paratest, one database will be created for each process. If you want to clean up these databases at the end of the tests, use the runner provided. First, register the runner alias in your composer.json file, something like this:
Now, run composer dump -o, and then you can use the runner, like so:
This will clean up the test databases after your test finishes running.
This package also gives you the following Artisan commands:
php artisan db:createphp artisan db:dropphp artisan db:recreate
Use it wisely.
Testing
Changelog
Please see CHANGELOG for more information what has changed recently.
Contributing
Please see CONTRIBUTING for details.
Security
If you discover any security related issues, please email [email protected] instead of using the issue tracker.
Credits
- Tony Messias
- All Contributors
License
The MIT License (MIT). Please see License File for more information.
Laravel Package Boilerplate
This package was generated using the Laravel Package Boilerplate.
