https://github.com/socialengine/setup-test-db
Get efficient with seeding your database for tests in Laravel
https://github.com/socialengine/setup-test-db
Last synced: about 1 year ago
JSON representation
Get efficient with seeding your database for tests in Laravel
- Host: GitHub
- URL: https://github.com/socialengine/setup-test-db
- Owner: SocialEngine
- License: mit
- Created: 2015-01-02T01:46:24.000Z (over 11 years ago)
- Default Branch: master
- Last Pushed: 2016-12-27T20:31:08.000Z (over 9 years ago)
- Last Synced: 2025-03-24T14:07:25.663Z (over 1 year ago)
- Language: PHP
- Size: 172 KB
- Stars: 9
- Watchers: 6
- Forks: 2
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
Setup Test DB Command for Laravel
====
[](https://packagist.org/packages/socialengine/setup-test-db) [](https://packagist.org/packages/socialengine/setup-test-db)
Integration tests in laravel are great, but the common way to maintain the database is a giant time sink
of re-seeding and re-migrating for every single test.
This command and bootstrap file aims to remove the needless reseeding and migrating (since you're using
transactions anyways, right?) for every test and instead gives your tests a "clean" migrated and seeded db.
Works with `sqlite` and any others supported by Eloquent.
## Installation
Require this package in composer:
```
$ composer require socialengine/setup-test-db
```
After updating composer, add the ServiceProvider to the providers array in `app/config/app.php`.
```
'SocialEngine\TestDbSetup\ServiceProvider',
```
Add a `bootstrap/testing.php` or copy from `vendor/socialengine/setup-test-db/bootstrap/testing.php`
```php
```
Remove all the migration stuff from your `TestCase.php`
Finally, run your tests in 1/3 the time they used to.
You can also publish the config-file to change seeder class used and enable truncation.
```
$ php artisan config:publish socialengine/setup-test-db
```
## Further reading and inspiration
Most of this is based on the work outlined by Chris Duell in his
[Speeding up PHP unit tests 15 times](http://www.chrisduell.com/blog/development/speeding-up-unit-tests-in-php/)
blog post:
> An app I’m currently working on has less that 50% code coverage, and the tests took over 35 seconds to complete.
>
> It was enough for me to no longer bother consistently running tests, which almost defeats the purpose of self
> testing code. Until I got fed up enough to spend the time on speeding up the tests,
> **by fifteen times** (and almost halving memory usage).
## License
MIT