Incorporating my custom assertion into Laravel's base TestCase class is something I'm working on. Here is a snippet of what it looks like:
<?php
namespace Tests\Mine;
use Tests\TestCase;
class SomeTest extends TestCase {
public function testSomethingIsWorking(): void {
$this->assertSomething("foo", "bar");
}
}
<?php
namespace Tests;
use Illuminate\Foundation\Testing\TestCase as BaseTestCase;
class TestCase extends BaseTestCase {
public function assertSomething($foo, $bar): void {
$this->assertSomethingElse($foo, $bar);
}
public function assertSomethingElse($foo, $bar): void {
if ($foo !== $bar) {
$this->fail("Some message here");
}
}
}
Despite functioning correctly, when running artisan test, any failure triggers the display of the context within TestCase::assertSomethingElse(). This means that the precise location within the failing test script is not highlighted. The output generally resembles this:
FAILED Tests\Mine > something is working AssertionFailedError
Some message here
at tests/TestCase.php:10
9 | if ($foo !== bar)
➜ 10 | $this->fail("Some message here");
11 | }
1 tests/TestCase.php:10
2 tests/TestCase.php:5
This behavior seems specific to Laravel; running just vendor/bin/phpunit suppresses contextual information and only traces back to the originating test script.
Is there a method to configure artisan test to display the relevant lines from
SomeTest::testSomethingIsWorking()