Generating new test with --unit flag is not importing the correct TestCase Class

@martinbean But how can I use the withoutExceptionHandling method if I use the default import?

@Jonjie There shouldnt be any exception handling as you arent using laravel. But you can catch them with phpunit if you want.

$this->expectException(MyException::class);

Maybe show the test and the problem

@Jonjie You can’t, because you shouldn’t be using that method. Again, unit tests should be able to be ran without the framework.

@Sinnbeck Please see my code below:

/** @test */
public function it_has_a_path()
{
    $this->withoutExceptionHandling();
    $product = Product::factory()->create();
    
    $this->assertEquals($product->path(), $product->path());
}

But when I put the class from PHPUnit back, I always get an error.

1. Tests\Unit\HomeProductTest::it_has_a_path InvalidArgumentException: Unknown format "words"

@Jonjie you are trying to create a product which means using the database, which means it isn't a unit test. Martin already mentioned this

Also why are you comparing it to it self? Is that a mistake?

@Sinnbeck Yeah, but why Jeffrey Way is using Tests\TestCase instead of PHPUnit\Framework\TestCase for his unit tests?

@Jonjie You would need to ask him. I personally think that is bad practice as the unit test is then no longer a test of a single unit :)

@Sinnbeck Thanks for the input, appreciate it :)

@tykus Please see my code below:

/** @test */
public function it_has_a_path()
{
    $this->withoutExceptionHandling();
    $product = Product::factory()->create();
    
    $this->assertEquals('/api/products/' . $product->id, $product->path());
}

But when I put the class from PHPUnit back, I always get an error.

1. Tests\Unit\HomeProductTest::it_has_a_path InvalidArgumentException: Unknown format "words"

@Jonjie you should not use the Factory (and database) to perform a Unit Test. Also, your assertion is nonsense.

/** @test */
public function it_has_a_path()
{
    $product = new Product;

    $this->assertEquals('some/path', $product->path());
}

@tykus I'm following Jeffrey's tutorial: https://laracasts.com/series/build-a-laravel-app-with-tdd

Meaning, his tests were also nonsense? Now, I'm a bit confused

@Jonjie did he actually assert that $product->path() equals $product->path()?

And also, does his Unit test class extend the PHPUnit\Framework\TestCase or the Tests\TestCase?

@tykus Sorry for the old code, but he's using factory here

@Jonjie so the Unit test must be using the Tests\TestCase base class? Otherwise, he could not be using framework features.

@tykus Yes, he's using Tests\TestCase. Is it okay to use factory (and database) when doing unit tests?

@Jonjie ok, well there you go then... there will be dissenting opinions on whether this is a true Unit test; I would argue it is not because you are not isolating the "unit". But I also understand that this type of test would be better than no test at all, so go for it if it works for you.

If you want the framework conveniences, the you must CreateApplication (which the Tests\TestCase class does, but PHPUnit\Framework\TestCase doe not.

Aside, the assertion still is nonsense... IMHO!