This is the bug I'm currently getting running on the 3.0.x@dev:

Illuminate\Container\BindingResolutionException: Target [Illuminate\Contracts\Debug\ExceptionHandler] is not instantiable. in vendor/laravel/framework/src/Illuminate/Container/Container.php on line 792

Hi,

I have some code in a package which throws exceptions in the boot method of the service provider if invalid config is provided.

I know I can set config in the getEnvironmentSetup method but I want to set individual configs with invalid values on a per-test basis in order to test that the exceptions are being thrown correctly if .

Is there a way I can do this?

I tried mocking Config::get() but it didn't work.

Thanks

Exception:

{"error":{"type":"ErrorException","message":"require(D:\\laravel\workbench\XX\XX\vendor\\orchestra\\testbench\\src\\fixture\\app\/start\/artisan.php): failed to open stream: No such file or directory"," file":"D:\\laravel\\workbench\\XX\\XX\\vendor\\laravel\\framework\\src\\Illuminate\\Console\\start.php","line":57}}

Reference: http://forums.laravel.io/viewtopic.php?pid=47727#p47727

I want to use Unittests within a new package and therefore I added

"require-dev": {
        "orchestra/testbench": "2.0.*@dev"
}

to my composer.json. After an composer update and a phpunit I get the following error.

PHP Fatal error:  Class 'Illuminate\Foundation\Testing\TestCase' not found in /home/chris/code/l4-survey/vendor/orchestra/testbench/src/Orchestra/Testbench/TestCase.php on line 10

It seems like the dependencies are not loaded correctly - maybe there is a missing requirement.

Can you tag a stable 2.2 version for Laravel 4.2 please.

Thank you for testbench! I've run into a snag. I'm trying to test a package in my workbench that creates a route with a filter:

Route::filter( 'my_filter', function( $route ) {
    $bar = $route->getParameter( 'bar' );
    if ( ! class_exists( $bar ) ) return Response::json( [ 'message' => 'error' ], 400 );
});

Route::get( 'foo/{bar}', [ 'before' => 'my_filter', function( $bar ) {
    $bar = new $bar();
});

My test case looks like:

public function testBarExists() {
    $this->call( 'GET', 'foo/test' ); // where 'test' is not an existing class
    $this->assertResponseStatus( 400 );
}

It appears that when I run my test, the filter is not being executed because I get the error Class 'test' not found... triggered from the line $bar = new $bar(); If I change my route to:

Route::get( 'foo/{bar}', [ 'before' => 'my_filter', function( $bar ) {
    if ( ! class_exists( $bar ) ) return Response::json( [ 'message' => 'error' ], 400 );
    $bar = new $bar();
});

Then the test passes as expected. Am I missing a configuration setting or something that prevents the testing environment from running my filter? My actual filter is quite a bit longer and has many other things that it checks. I'll also be using the filter on several different routes, so it would not be DRY to just copy the error checking code into each of my routes.

Thanks!
Morgan

PHP Fatal error: Call to undefined method Illuminate\Routing\Router::disableFilters() in /home/travis/build/orchestral/testbench/tests/RouteTest.php on line 12

With the introduction of stack/builder, the application bootstrap process has include some changes which I would believe broke 2.1.

Today I wanted to fix a bug in https://github.com/schickling/laravel-backup, cloned the repo, installed deps via composer and ran phpunit. I got:

PHP Fatal error:  Class 'Illuminate\Exception\LiveServiceProvider' not found in /Users/johannes/Desktop/laravel-backup/vendor/laravel/framework/src/Illuminate/Foundation/ProviderRepository.php on line 123

I suspect Testbench to be the reason, since the error only occurs for tests which extend Orchestra\Testbench\TestCase

Since installing this I now get these errors:

PHP Fatal error:  Cannot redeclare Mockery_3_Illuminate_Support_Facades_View::shouldReceive() in /home/vagrant/www/workbench/tectonic/shift/vendor/mockery/mockery/library/Mockery/Loader/EvalLoader.php(16) : eval()'d code on line 690

This is a result of mocking out the View class in mockery:

$this->mockView = m::mock('View');

How should I now approach these situations?

Is the laravel dependency via composer really needed? Aren't some packages of the laravel-framework (illuminate components) enough? Would be more lightweight and feels "cleaner".

Hi,

This is the first time I (try to) use this package to use within the laravel workbench, but I get stuck on this error:

PHP Fatal error:  Call to undefined method Illuminate\Foundation\Providers\ArtisanServiceProvider::when() in /laravelapp/workbench/myvendorname/mypackagename/vendor/laravel/framework/src/Illuminate/Foundation/ProviderRepository.php on line 134

This issue seems to be already noted here laravel/framework#3282 so I tried following their solution by upping testbench's illuminate/support requirement to 4.* but I don't seem to get it working.

I'm writing a package from the workbench. Orchestra\Testbench works great, and I have no trouble running my tests from the command line using phpunit.

However, if I try to visit the parent app in the browser I get a fatal error:

Fatal error: Cannot redeclare crypt_random_string() (previously declared in 
/path/to/myapp/vendor/phpseclib/phpseclib/phpseclib/Crypt/Random.php:61) in 
/path/to/myapp/workbench/morphatic/qualtrics/vendor/phpseclib/phpseclib/phpseclib/Crypt/Random.php on line 246

Pretty sure the problem is that the parent app is trying to load Laravel again from the workbench. Is there a setting or workaround to prevent this?

It may sound silly but I spend 4 hours to understand how to setup the configurations and the migrations of my first laravel package. I was a big relief when I discovered this file: tests/DatabaseFixtureTest.php

It would be very helpful (and I wouldn't spend this time searching) if you had a small chapter in the read me file, with title "Example", linking to the mentioned file.

Thanks for this great package :)

I have a controller in my workbench that extends Laravel's BaseController. This is fine when running routes in browser but when running a unit test and making a http request with:

$this->call('GET', '/workbench-route');

I get an error stating BaseController cannot be found. phpunit is running with the bootstrap switch set to vendor/autoload.php.

Do I need some additional config to test controllers with testbench?

see https://scrutinizer-ci.com/g/orchestral/testbench/inspections/7a1eff04-d43b-42d8-bb82-2a9806d830d4/issues/files/src/Testbench/Traits/PHPUnitAssertionsTrait.php?status=new&orderField=path&order=asc#inspectioncomment-88874799

Could not fetch https://api.github.com/repos/orchestral/phpseclib, enter your GitHub credentials to go over the API rate limit.

I looked through the closed issues and a see a few issues regarding other test frameworks. I was wondering if you would be willing to make a doc section for the frameworks and how your package would interact with them.

phpspec, phpunit, codeception, behat

Thank you either way :)

Following your example I have been trying to run several migrations as follows:

public function setUp() {
    parent::setUp();

    // enable route filters
    $this->app[ 'router'  ]->enableFilters();

    // run package-specific migrations to create Sentry 2 tables
    $this->app[ 'artisan' ]->call( 'migrate', [
        '--package'  => 'cartalyst/sentry',
        '--database' => 'testbench',
    ]);

    // run custom migrations and seed the DB
    $this->app[ 'artisan' ]->call( 'migrate', [   // this is line 30
        '--path'     => '../../tests/database/migrations',
        '--database' => 'testbench',
        '--seed'     => '',
    ]);
}

When I run my tests I get:

PHP Fatal error: Call to undefined method Illuminate\Console\Application::call() in /path/to/MyTest.php on line 30

To investigate this I inserted the following after every reference to $this->app in setUp:

echo get_class( $this->app[ 'artisan' ] ) . "\n"; 
echo method_exists( $this->app[ 'artisan' ], 'call' ) ? "'call' exists\n" : "no 'call' method\n";

I got the following result:

Illuminate\Foundation\Artisan 'call' exists Illuminate\Foundation\Artisan 'call' exists Illuminate\Console\Application no 'call' method

It appears that after the first call to $this->app['artisan']->call() the $this->app object gets converted into type Illuminate\Console\Application. I'm not familiar enough with Laravel to know if this is expected behavior, or what/if other issues will be caused with testing down the line. I was able to work around the issue as follows:

public function setUp() {
    parent::setUp();

    // enable route filters
    $this->app[ 'router'  ]->enableFilters();

    // create an artisan object for running migrations
    $artisan = $this->app->make( 'artisan' );

    // run the migrations to create Sentry 2 tables
    $artisan->call( 'migrate', [
        '--package'  => 'cartalyst/sentry',
        '--database' => 'testbench',
    ]);

    // run custom migrations and seed the DB
    $artisan->call( 'migrate', [
        '--path'     => '../../tests/database/migrations',
        '--database' => 'testbench',
        '--seed'     => '',
    ]);
}

My apologies if this is not an issue. Thanks for a great package.

Hello, i'm using orchestral/[email protected] inside a workbench in laravel 4.1. i'm trying to run artisan from a unit test to prepare the database for my integration tests. The code works perfectly from the console as you can see:

jacopo:pacchetti_palmabit intrip$ php artisan migrate --env=testing --database=authentication
Migrated: 2014_02_19_095545_create_users_table
Migrated: 2014_02_19_095623_create_user_groups_table
Migrated: 2014_02_19_095637_create_groups_table
Migrated: 2014_02_19_095645_create_user_throttle_table
Migrated: 2014_02_19_131843_prova

While from the unit test the code runs with no error, but doesn't create any table. Here is the code in the test:

<?php
use Artisan;

class DbTestCase extends TestCase
{
    public function setUp()
    {
        parent::setUp();

        $artisan = $this->app->make( 'artisan' );

        $artisan->call('migrate',[
                                 '--env'  => 'testing',
                                 "--database" => "authentication"
            ]);
    }
}

Not only my migrations are not working but all the migrations i try to use.
I think it's a bug, please update me with some info. Thanks.

Doesn't appear to call any of the service providers that the one you've added provides?

We have our main package provider, which also provides about 10 others - but these never seem to get loaded within testbench. Any ideas why or how to resolve this? I can add them all manually, but that seems a bit strange to have to do it in testbench as well?

This could help development on process.

Hello,
I'm starting to use Behat for some functional testing and would love to be able to boot a Laravel app from this package and use it with Behat. This package being the de-facto standard for testing Laravel packages, seems like a good fit for such feature.
If you don't plan on having said feature I would then like, with your consent, to take inspiration from your package to implement my own.

I have installed the testbench package as per the instructions on the repo's README file. Then when I cd in to my packages tests directory and run:

phpunit MyTestClass.php

I get:

Fatal error: Class 'Orchestra\Testbench\TestCase' not found

It throws the error on the following line:

class MyTestClass extends \Orchestra\Testbench\TestCase

My composer.json looks like:

{
    "name": "quasimodal/uploadyoda",
    "description": "",
    "authors": [
        {
            "name": "Peter Caulfield",
            "email": "[email protected]"
        }
    ],
    "require": {
        "php": ">=5.3.0",
        "illuminate/support": "4.1.x"
    },
    "require-dev" : {
        "orchestra/testbench" : "2.1.*",
        "mockery/mockery": "0.8.0"
    },
    "repositories": [
            {
                "type": "vcs",
                "url": "git://github.com/orchestral/phpseclib.git"
            }
        ],
    "autoload": {
        "psr-0": {
            "Quasimodal\\Uploadyoda": "src/"
        },
        "classmap" : [ 
            "src/migrations",
            "src/controllers",
            "src/models"
        ]
    },
    "minimum-stability": "dev"
}

Hey @crynobone, this user might need your help in the forums:

http://forums.laravel.io/viewtopic.php?id=11620

Hi,

I'm seeding an sqlite database for my 'testing' environment via http://laravel.com/docs/migrations#database-seeding

Then when I try to run the tests it says it knows nothing about the connections I have in app/config/testing/database.php, eg:

'connections' => array(
    'sqlite' => array(
        'driver'   => 'sqlite',
        'database' => app_path() . '/database/testing.sqlite',
        'prefix'   => '',
    ),
    'sqlite2' => array(
        'driver'   => 'sqlite',
        'database' => app_path() . '/database/testing2.sqlite',
        'prefix'   => '',
    ),
),

When I debug this in laravel/framework/src/Illuminate/Database/DatabaseManager.php, I instead see a list of connections from:
orchestra/testbench/src/fixture/app/config/database.php

Could you point me in the right direction as to how to get this to read my app/config/testing/database.php rather than the orchestra one?

If I use mysql no problems. But if I use in sqlite in memory database there are problems....
If I not use testbench package with memory database its works perfect.

I added the require statement and then from the package root, i did composer update and it installed a bunch of goodies into the vendors dir.

Is that what you expected to happen?

Laravel provides a way of using environment-specific configuration files as a way to set up environment variables that don't get committed to a central repository. Is there a way to use those files while running tests from testbench?

Was wondering if it's possible to use Model::ShouldReceive() to mock Eloquent object when extending testBench?

I've followed the instructions within workbench and it works great... however when I apply the same repository to my project as instructed it fails to resolve the issue. Here's my composer.json

{
    "name": "laravel/laravel",
    "description": "The Laravel Framework.",
    "keywords": ["framework", "laravel"],
    "license": "MIT",
    "require": {
        "laravel/framework": "4.1.*",
        "twilio/sdk": "3.12.*",
        "nesbot/Carbon": "1.8.*",
        "fzaninotto/faker": "1.4.x-dev"
    },
    "require-dev": {
        "way/generators": "dev-master",
        "way/laravel-test-helpers": "dev-master",
        "mockery/mockery": "dev-master",
        "codeception/aspect-mock": "*",
        "phpunit/phpunit": "3.7.*@dev",
            "barryvdh/laravel-ide-helper": "1.*",
            "anahkiasen/rocketeer": "dev-develop",
            "hipchat/hipchat-php": ">=1.0.0"
    },
    "autoload": {
        "classmap": [
            "app/commands",
            "app/controllers",
            "app/models",
            "app/database/migrations",
            "app/database/seeds",
            "app/tests/TestCase.php"
        ],
        "psr-0": {
                    "Broadcasts": "app/lib",
                    "Facades": "app/lib",
                    "Deployment": "app/lib"
        }
    },
    "scripts": {
        "post-install-cmd": [
            "php artisan optimize"
        ],
        "post-update-cmd": [
            "php artisan clear-compiled",
            "php artisan ide-helper:generate",
            "php artisan optimize"
        ],
        "post-create-project-cmd": [
            "php artisan key:generate"
        ]
    },
    "config": {
        "preferred-install": "dist"
    },
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/changwuf31/remote"
        },
        {
            "type": "vcs",
            "url": "git://github.com/orchestral/phpseclib.git"
        }
    ],
    "minimum-stability": "dev"
}

I've also tried deleting vendor/phpseclib and dumping autoload to force it to fetch a new one.

As explained in #4

I followed the great example you guys have over here: https://github.com/orchestral/testbench/blob/master/tests/DatabaseFixtureTest.php

So far, so good - except for migrations. If I run it manually from the command line, I can see that it works, but if I try and do it from the artisan->call method, my sanity check below it fails (no table exists), meaning that either the migrations never ran correctly, or the connection to sqlite is dropping before I run the next query.

Here's my current code (mostly taken from the example):

public function setUp()
{
    parent::setUp();

    $artisan = $this->app->make('artisan');

    $artisan->call('migrate', [
        '--database' => 'test',
        '--path' => '../../src/migrations'
    ]);

    // Sanity check. This will fail if migrations failed.
    DB::table('roles')->get();
}

As you can see, this is pretty much identical to the example provided in the docs, except for a different database name. I've tried using testbench also, no go.

As far as I can tell - I don't think you can call paths like that, but I've tried every other possible example, including paths from application root, absolute paths, relative paths.etc. all to no avail.

Any ideas what's going on? This is my database configuration:

protected function getEnvironmentSetUp($app)
{
    // reset base path to point to our package's src directory
    $app['path.base'] = __DIR__ . '/../../';

    $app['config']->set('database.default', 'test');
    $app['config']->set('database.connections.test', array(
        'driver'   => 'sqlite',
        'database' => ':memory:',
        'prefix'   => ''
    )
}

Hi,
I'm currently having issues by using 3.0 Testbench version on the Laravel 5 conversion of a package of mine.

The package is Message Board and Travis gets my same error.

The composer.json is quite simple

"require": {
    "php": ">=5.4.0",
    "chromabits/purifier": "dev-master",
    "laravel/framework": "~5.0",
    "michele-angioni/support": "~2.0"
},
"require-dev": {
    "mockery/mockery": "dev-master",
    "orchestra/testbench": "3.0.*",
    "phpunit/phpunit": "~4.1",
    "sami/sami": "dev-master"
},

This is one of the failing tests : as you can see, the test boilerplate is most copied from your example.
However, it already fails at the parent::setUp() call, in the setUp() method.

Tracking down the issue it happens in the $this->resolveApplicationConfiguration($app) call in ApplicationTrait and the failing line is n. 199 $app->make('Illuminate\Foundation\Bootstrap\LoadConfiguration')->bootstrap($app); during the Application bootstrap.

That line calls in the LoadConfiguration class

date_default_timezone_set($config['app.timezone']);

and it obviously fails because app.timezone is still not set.
Is there something I miss? Is there an error somewhere?

Thanks for your help

Hey there.

Just curious if there's anything special we need to do when testing routes?

Whenever I do the following:

$this->call('GET', 'roles');

It always returns a 404, despite the fact that I can access that route in the browser. I understand filters are disabled, so that's fine. When I run php artisan routes, I see the following:

GET|HEAD roles/(:num)
PUT roles/(:num)
GET|HEAD roles

So I should be seeing it all, but for some reason via tests it doesn't seem to register the routes?

Can you clarify what you mean?

Do you want us to remove the

    "illuminate/support": "4.0.x",

line from the require block before doing the composer update call?

Amongst the latest updates, the configuration handling has been changed in Laravel, meaning that loading configuration files, no longer makes use of Illuminate\Config\FileLoader (which no longer exists either). Running tests is thereby impossible.

This defect occurs in the resolveApplicationCore method, in the ApplicationTrait

I was having an issue where getEnvironmentSetUp() method is never called. Did a bit of digging and the issue appears to only occur when Orchestra\Foundation\Reminders\ReminderServiceProvider is included in getPackageProviders().

In Orchestra\Testbench\TestCase class you have the following lines:

$providers = array_merge($this->getApplicationProviders(), $this->getPackageProviders());
$app->getProviderRepository()->load($app, $providers);

$this->getEnvironmentSetUp($app);

That last line is never reached if Orchestra\Foundation\Reminders\ReminderServiceProvider is in getPackageProviders().

I thought If I were writing a package that depended on Orchestra, I should include all the Orchestra providers (from app/config/app.php) like so:

protected function getPackageProviders()
{
     return [
        'Orchestra\Asset\AssetServiceProvider',
        'Orchestra\Auth\AuthServiceProvider',
        'Orchestra\Debug\DebugServiceProvider',
        'Orchestra\View\DecoratorServiceProvider',
        'Orchestra\Extension\ExtensionServiceProvider',
        'Orchestra\Facile\FacileServiceProvider',
        'Orchestra\Html\HtmlServiceProvider',
        'Orchestra\Memory\MemoryServiceProvider',
        'Orchestra\Support\MessagesServiceProvider',
        'Orchestra\Notifier\NotifierServiceProvider',
        'Orchestra\Optimize\OptimizeServiceProvider',
        'Orchestra\Extension\PublisherServiceProvider',
        'Orchestra\Foundation\Reminders\ReminderServiceProvider',
        'Orchestra\Resources\ResourcesServiceProvider',
        'Orchestra\Foundation\SiteServiceProvider',
        'Orchestra\Translation\TranslationServiceProvider',
        'Orchestra\View\ViewServiceProvider',
        'Orchestra\Widget\WidgetServiceProvider',

        'Orchestra\Foundation\ConsoleSupportServiceProvider',
        'Orchestra\Foundation\FoundationServiceProvider',

        'Path\To\MyServiceProvider',
    ];
}

Is this an issue with your ReminderServiceProvider or is it never supposed to be included in getPackageProviders?

As example. I want to create some messaging-package for laravel4 (https://github.com/inkrement/l4-messenger). Therefore I want to test the new models. Would It be possible to change the database-settings (use sqlite), run migrations and then test the models?

Is there any documentation hidden away for the new Behat integration? I'm using behat without Orchestra at the moment and would love to move it into my application. If there is not documentation could someone offer some guidance on how to achieve this?

The cache and session config files should be like those in the testing environment folder in Laravel. The drivers should be set to array and not file. There can be collision between tests when the cache and sessions would be expected to be cleared since the application is refreshed, but since they're stored in files they are persisted between all tests in a suite and even between instances of running test suites. I can make PR if that would be helpful, it's a quick edit.

In your readme add an example of how to access your package in a unit test...

The new Laravel 4.3 fixture is not supported yet.

Whenever I try to call $this->action('GET', 'MyController@index');

I get InvalidArgumentException: Unknown action [MyController@index]

My controller is located in workbench/vendor/app/src/controllers and src/controllers has been added to classmap on my composer.json file.

Any ideas why this may be happening?