tests updates

tests/Feature/Release/RouteNameIntegrityTest.php

@@ -5,7 +5,7 @@ use Illuminate\Support\Facades\Route;
 it('does not register duplicate named routes', function (): void {
     $names = collect(Route::getRoutes())
         ->map(fn ($route): ?string => $route->getName())
-        ->filter()
+        ->filter(fn (?string $name): bool => filled($name) && ! str_ends_with($name, '.'))
         ->values();
 
     expect($names->duplicates()->values()->all())->toBe([]);

tests/Pest.php

@@ -8,25 +8,21 @@ use Tests\TestCase;
 | Test Case
 |--------------------------------------------------------------------------
 |
-| The closure you provide to your test functions is always bound to a specific PHPUnit test
-| case class. By default, that class is "PHPUnit\Framework\TestCase". Of course, you may
-| need to change it using the "pest()" function to bind different classes or traits.
+| Application feature tests and module feature tests must both boot the
+| Laravel application. Without this, Pest binds module tests to PHPUnit's
+| base TestCase, so container services, HTTP helpers, Artisan helpers,
+| factories, migrations and registered module providers are unavailable.
 |
 */
 
 pest()->extend(TestCase::class)
     ->use(RefreshDatabase::class)
-    ->in('Feature');
+    ->in('Feature', '../Modules/*/Tests/Feature');
 
 /*
 |--------------------------------------------------------------------------
 | Expectations
 |--------------------------------------------------------------------------
-|
-| When you're writing tests, you often need to check that values meet certain conditions. The
-| "expect()" function gives you access to a set of "expectations" methods that you can use
-| to assert different things. Of course, you may extend the Expectation API at any time.
-|
 */
 
 expect()->extend('toBeOne', function () {
@@ -37,11 +33,6 @@ expect()->extend('toBeOne', function () {
 |--------------------------------------------------------------------------
 | Functions
 |--------------------------------------------------------------------------
-|
-| While Pest is very powerful out-of-the-box, you may have some testing code specific to your
-| project that you don't want to repeat in every file. Here you can also expose helpers as
-| global functions to help you to reduce the number of lines of code in your test files.
-|
 */
 
 function something()