feat: add support for using Finder objects for uses()

[owenvoke]

Q	A
Bug fix?	no
New feature?	yes
Fixed tickets	#...

This came up on Discord where it was asked whether it was possible to provide something such as globs (e.g. **/Feature) to the uses()->in() call. This will basically throw a ShouldNotHappen exception if the Finder class doesn't exist, and the usual uses()->in() call can be used as normal.

For example, here's how you could specify all Feature subdirectories to use a specific testcase class.

use Symfony\Component\Finder\Finder;

uses(Tests\TestCase::class)->inFinder(
    Finder::create()
        ->name('Feature')
        ->directories()
        ->in(__DIR__)
);

[devatreides]

You can just set the dir name (in this case, "__DIR__") and the Finder class will keep looking recursively.

use Symfony\Component\Finder\Finder;

uses(Tests\TestCase::class)->inFinder(
    Finder::create()
        ->name('Feature')
        ->directories()
        ->in(__DIR__)
);

Just to be clear, the parameter is a Finder instance for not add Symfony/Finder to Pest dependencies?

[owenvoke]

Yeah, the parameter is a Symfony\Component\Finder\Finder instance, but I wasn't sure whether to add it as a dependency for now. It's just suggested if people want to use it.

[nunomaduro]

Can’t we make the “in” method accept a string or a instance of Finder?

[nunomaduro]

Also, can you add a test for this? Maybe add a new folder that extends a specific test case.

[nunomaduro]

cc @owenvoke

[owenvoke]

Apologies, I'd lost track of this. I'd thought about adding it directly to the in() call. I guess I can do that. 👍🏻

[nunomaduro]

@owenvoke What's the current state of this pull request?

[nunomaduro]

No plans for this, thanks!