Why not just use orchestra/testbench, which was design for this type of testing. http://orchestraplatform.com/docs/latest/components/testbench for detail
Jun 16, 2015
1
Level 4
travis configuration for laravel packages
I'm trying to piece together a configuration for laravel packages. Does anyone have experience with this for laravel 5.1+?
Both use the ability to append to the configuration from an environment specific config directory. Is there a way to do the same in 5.1+?
So far I have, but before I start testing functionality and need thousands commits to fix this, perhaps people with travis experience can shed some light on this setup:
language: php
php:
- 5.5
- 5.6
- hhvm
before_install:
- composer self-update
addons:
hosts:
- system.hyn.me
- tenant.hyn.me
install:
- composer create-project laravel/laravel
- cd ./laravel
- composer require hyn-me/multi-tenant ~0.1.0
- composer update
before_script:
- cp .env.travis .env
- export APP_ENV="testing"
- php artisan migrate -q -n --path ./vendor/hyn-me/multi-tenant/src/migrations
- cd ./vendor/hyn-me/multi-tenant
script: phpunit
Trying to make this work for http://github.com/hyn-me/multi-tenant
Please or to participate in this conversation.