When requiring this package in a Laravel package which only supports version 5.5 it still installs an older version of orchestra/testbench.

I've provided a failed job from Travis: https://travis-ci.org/vinkla/laravel-algolia/jobs/271252437

If I specify the exact version of orchestra/testbench in my package it works fine. Though, it shouldn't be necessary right?

Hello and thank you for this awesome package.

I don't know if it is an issue or it's me but when I test my ServiceProvider with the method assertIsInjectabl($name) and in the register method, I do:

$this->app->singleton('excel-importer.importer', function (Container $app) {
    $config = $app->config->get('excel-importer'); // return null :'( but $app->config is OK
    return new Importer($config);
});

It throws this exception:

The class 'Me\ExcelImporter\Importer' couldn't be automatically injected. Unresolvable dependency resolving [Parameter #0 [ <required> array $config ]] in class Me\ExcelImporter\Importer
Failed asserting that false is true.

Boot method of my service provider:

$source = realpath(__DIR__ . '/../config/excel-importer.php'); // Path is OK
$this->publishes([$source => config_path('excel-importer.php')]);
$this->mergeConfigFrom($source, 'excel-importer');

Many thanks

Added support for PHPUnit 7.0 which will be released in two weeks.

https://twitter.com/s_bergmann/status/954245050392866816

https://github.com/orchestral/testbench-core/pull/7 https://github.com/GrahamCampbell/Laravel-TestBench-Core/pull/4

Hey

This is essentially a duplicate of https://github.com/GrahamCampbell/Laravel-TestBench-Core/issues/12 as the same change was made in both packages

Essentially, we can't use the new v5.6 release as we have an implementation of getServiceProviderClass that has the $app parameter. We support a wide range of PHP versions, so have to be compatible with multiple versions of testbench & testbench-core. If we remove the $app parameter then our code isn't compatible with earlier versions of the library but if we keep it then we're not compatible with the latest version

Is there a way we can support v5.6 with a single AbstractTestCase? If not, is it possible to revert this change?

Thanks!