CODEWITHSUNDEEP
unit-testinglaravelworkbench
driechel
driechel

Reputation: 3453

Laravel workbench unit test

What is the way to test my packages in workbench. If I write a unit test then no classes are autoloaded. So this means that:

<?php

use \Mockery as m;

class ExampleTest extends TestCase {

public function tearDown()
{
    m::close();
}

/**
 * A basic functional test example.
 *
 * @return void
 */
public function testShouldReturnValidServer()
{

    $mock = m::mock('MailChimp[sendCurl]');

    MailChimp::listSubscribe( array( 'id' => 'c79a023ff2', 'email_address' => '[email protected]'));

   }
}

results in a error saying that class TestCase is not found. When I add class TestCase to the autoload in my composer.json (the one in my package folder) the class is available. However then I get the next error that "Illuminate\Foundation\Testing\TestCase" is not available etc. etc. So my question is what should I autoload in my composer.json in my package folder? Everything just like in my main composer.json or is there some other way that I am missing.

I know that in the manuel it says"

You may git init from the workbench/[vendor]/[package] directory and git push your package straight from the workbench! This will allow you to conveniently develop the package in an application context without being bogged down by constant composer update commands.

However I do not understand this. Can someone explain what is meant with this? By the way I am familiar with git. I just do not get the context.

EDIT1 As far I understand now is that you push your package to your repository and then include it in your main composer.json as package. I just do not see how this is helpful when developing. Hopefully I understand this wrong.. :)

EDIT2 I was wrong. You keep your package in workbench until it stable. Just like Nils pointed out below.The question still remains though. How do I create an environment in which I can unit test with the app started. I mean like testing a model where I can mock the facades etc. Or is doing this in the workbench bad practice?

Upvotes: 1

Views: 3096

Answers (3)

Fixspec
Fixspec

Reputation: 420

If you don't mind merging the results of your workbench testing with the results of your main application, you can simply add extra directories to your main phpunit.xml in your laravel root like this:

<testsuites>
    <testsuite name="Application Test Suite">
        <directory>./app/tests/phpunit/</directory>
        <directory>./workbench/vendor/packageOne/tests/</directory>
        <directory>./workbench/vendor/packageTwo/tests/</directory>
    </testsuite>
</testsuites>

Then in the tests folder of your package, place your phpunit tests as normal, along with the TestCase.php file, adjusting the createApplication() function to be:

<?php

class TestCase extends \Illuminate\Foundation\Testing\TestCase {

public function createApplication()
{
    $unitTesting = true;
    $testEnvironment = 'testing';
    return require './bootstrap/start.php';
}

Make sure your package composer.json auto-loads that TestCase.php file like so:

"autoload": {
    "classmap": [
        "tests/phpunit/TestCase.php"           
    ]
}

Run composer dump-autoload -o to get everything aligned and then you should be able to run phpunit from your laravel root and it will test both your application and your packages.

Upvotes: 2

marcanuy
marcanuy

Reputation: 23972

Extend from the proper namespace and you should be able to run tests from package dir.

class ExampleTest extends \Illuminate\Foundation\Testing\TestCase {
    ..
}

See also Laravels neat testing helpers in workbench?

Upvotes: 0

crynobone
crynobone

Reputation: 1814

I created a package for this purpose at https://github.com/orchestral/testbench

Upvotes: 7

Related Questions