pestphp / pestphp/pest

[Bug]: mutation testing fails if directory is called `Datasets`

Open
#1,415 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
PHP
Stars
11.7k
Forks
538
Avg merge
4d 11h
Merged PRs (30d)
8

Description

What Happened

I have a few Livewire components living in the App\Livewire\Datasets\ namespace, and therefore their tests are in the tests\Feature\Livewire\Datasets directory.

The tests all pass just fine, but when I run the mutation testing I get the following

   Pest\Exceptions\ShouldNotHappen 

  This should not happen - please create an new issue here: https://github.com/pestphp/pest.

  Issue: A dependency with the name `Pest\Mutate\Contracts\MutationTestRunner` cannot be resolved.
  PHP version: 8.4.8
  Operating system: Darwin
How to Reproduce
  • Create a Livewire component and its feature test
  • add the mutate() method to the test
  • rename directory where the tests lives to Datasets
  • run the mutation testing
Sample Repository

No response

Pest Version

3.8.2

PHP Version

8.4.8

Operation System

macOS

Notes

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure with Pest 3.8.2, PHP 8.4.8, and a test directory named Datasets, then compare it with the same test under another directory name. Trace the mutation-testing setup from the test using mutate() and investigate why Pest\Mutate\Contracts\MutationTestRunner cannot be resolved; done means mutation testing runs successfully for the Datasets directory.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.