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.

Hello, I'm trying to run my tests, that are creating a folder. I use the following to define the wanted path:

$this->testModulePath = __DIR__ . "/../Modules/{$this->testModuleName}";

When I dump this using dd I get : "/Users/nicolaswidart/Sites/Asguard/IndividualModules/Workshop/Tests/../Modules/TestingTestModule", which is correct.

Though when calling an artisan command that is suppose to generate it, it makes it under vendor/orchestra/testbench/fixtures/Modules/TestingTestModule

This is my getEnvironmentSetUp method:

protected function getEnvironmentSetUp($app)
{
    $app['path.base'] = __DIR__ . '/..';
}

Did I miss something ?

Thanks!

My package uses views with forms in it. I am using old() to get the old input if I send it back to the form. When I do this and try to run my tests I am getting the message Session not set on request

I am using v3.1 with Laravel 5.1

I have tried the following.

    protected function getEnvironmentSetUp($app)
    {
        $app['request']->setSession($app['session']->driver('array'));
    }

No luck!

What do I need to do?

• Testbench Version: 7.12.1

Description

Hi,

After I got the updated testbench version, I can not execute some commands successfully. For example, the following command throwing the error SQLSTATE[HY000] [2002] Connection refused.

vendor/bin/testbench migrate --database=sqlite --path=vendor/orchestra/testbench-core/laravel/migrations --path=../../../../database/migrations

I have set my own testbench.yaml file with the following database configuration but it seems that testbench-core ignores them.

DB_CONNECTION="sqlite" DB_DATABASE="database.sqlite"

How can I set the DB_CONNECTION parameter in testbench-core ? Is it possible to change the default configuration settings of testbench using any commands option?

Using factories does not work as intended in tests. Trying to call a factory results in the following error: Fatal error: Uncaught Error: Call to a member function define() on null

This is for orchestra v3.8

These are the TestCase, Test and factory files being used.

namespace Tests;

use Orchestra\Testbench\Concerns\WithFactories;
use Orchestra\Testbench\TestCase as BaseTestCase;

class TestCase extends BaseTestCase
{
    use WithFactories;

    protected function setUp(): void
    {
        parent::setUp();

        $this->withFactories(__DIR__.'/../src/database/factories');
    }

    protected function getPackageProviders($app): array
    {
        return [
            // providers
        ];
    }

    protected function getPackageAliases($app)
    {
        return [
            // aliases
        ];
    }
}

namespace Tests\Feature;

use App\User;
use Tests\TestCase;
use Illuminate\Foundation\Testing\WithFaker;

class UserTest extends TestCase
{
    use WithFaker;

    private $user;

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

        $this->artisan('migrate');

        $this->user = factory(User::class)->create();
    }
}

/** @var \Illuminate\Database\Eloquent\Factory $factory */
use App\User;
use Illuminate\Support\Str;
use Faker\Generator as Faker;

$factory->define(User::class, function (Faker $faker) {
    return [
        'first_name' => $faker->firstName,
        'last_name' => $faker->lastName,
        'email' => $faker->unique()->safeEmail,
        'email_verified_at' => now(),
        'password' => '', // password
        'remember_token' => Str::random(10),
    ];
});

Can you tell me what could possibly be wrong here? Is this an implementation error or a bug in orchestra itself?

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?

One of my tests fails with this message:

1) ViewTest::testCreateWithLocale
BadMethodCallException: Method Mockery_0_Illuminate_Routing_Router::getRoutes() does not exist on this mock object

.../aimeos-laravel/vendor/laravel/framework/src/Illuminate/Routing/RoutingServiceProvider.php:45
.../aimeos-laravel/vendor/laravel/framework/src/Illuminate/Container/Container.php:290
.../aimeos-laravel/vendor/laravel/framework/src/Illuminate/Container/Container.php:773
.../aimeos-laravel/vendor/laravel/framework/src/Illuminate/Container/Container.php:656
.../aimeos-laravel/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:642
.../aimeos-laravel/vendor/laravel/framework/src/Illuminate/Foundation/helpers.php:53
.../aimeos-laravel/src/Aimeos/Shop/Base/View.php:54
.../aimeos-laravel/tests/Base/ViewTest.php:33

It worked when the package was part of an application but since using the testbench package it fails. What could be the cause for this?

The test code is available at https://github.com/aimeos/aimeos-laravel/blob/master/tests/Base/ViewTest.php#L15-L34

I propose call getEnvironmentSetUp earlier so that people can make config modifications before all the service providers have booted.

~~If you want, I could put it here instead?~~ DONE

$app->make('Illuminate\Foundation\Bootstrap\RegisterProviders')->bootstrap($app);
$this->getEnvironmentSetUp($app);
$app->make('Illuminate\Foundation\Bootstrap\BootProviders')->bootstrap($app);

Exception: Missing orchestra/database in composer.json

"require": {
    "php": "^5.6|^7.0",
    "illuminate/database": "~5.2.0|~5.3.0|~5.4.0",
    "illuminate/support": "~5.2.0|~5.3.0|~5.4.0"
},
"require-dev": {
    "orchestra/testbench": "~3.0",
    "phpunit/phpunit": "^5.2"
},

Latest version of test bench require "orchestra/database": "~3.4.0", but latest release is 3.3.5!

Hi there,

I currently develop a package that writes some class files in a laravel application to speed up development.

When trying to test this, the class file will be written to vendor/testbench-core/fixtures/app. So after generation I have a class FooBar in vendor/testbench-core/fixtures/app/FooBar.php with namespace App.

Checking if file was written works like this

$this->assertFileExists(base_path('/app/FooBar.php'));

I now want to write the test if the generated class can be used (and other method tests for this generated class) to verify the correctness of the class stub. When I use

$foobar = new \App\FooBar();
$this->assertInstanceOf('App/FooBar', $foobar);

I get an error that the class \App\FooBar is not found.

How can I instantiate the class? Do I need some special composer autoload setup? Or should this be tested with a real and complete Laravel application?

Appreciate your help :)

Hello,

Thank you for all the work you have done on this fantastic package - it is really magnificent and super helpful.

I am in the process of upgrading one of my packages to be compatible with Laravel 5.2 and some of the integration tests look for validation errors to be triggered, Those errors seem to be handled differently in 5.2 than they were in 5.1 and this PR is intended to update the TestBench exception handler to match the new 5.2 framework exception handler.

Feel free to ignore this if you would prefer a different method - any advice you have would be appreciated.

Thanks!