Pest doesnt use PHPCS

[SirLouen]

Which is the coding standard for PEST? I don't see a phpcs.xml file in the repo. I wonder if there is a preferred PHPCS when writting tests for PEST that doesnt collide too much. I've noticed that PSR-1 is problematic for rules like PSR1.Files.SideEffects.FoundWithSymbols,

I saw this project to provide some sort of standarization worksome/pretty-pest but looks abandoned...

[ibamzjr]

For Pest itself, the repository's current linting contract is Laravel Pint plus Rector, not PHPCS.

The relevant Composer scripts are:

composer test:lint   # checks Rector and Pint without changing files
composer lint        # applies the configured fixes

You can see those scripts in composer.json, the project-specific Pint rules in pint.json, and the contributor workflow in CONTRIBUTING.md.

For an application's own Pest tests, Pest does not require a particular style tool. PHPCS is still fine if that is the team's standard, but PSR-1's "side effects" rule is a poor fit for Pest test files because top-level test declarations are executable by design. Scope or exclude that sniff for the tests directory, while keeping the rest of the rules you need, rather than changing valid Pest syntax to satisfy it.

So there is no need for a separate pretty-pest dependency when contributing to Pest core: use the repository's Composer scripts. In a downstream project, choose Pint or configure PHPCS around Pest's declarative test style.

[SirLouen]

So there is no need for a separate pretty-pest dependency when contributing to Pest core: use the repository's Composer scripts. In a downstream project, choose Pint or configure PHPCS around Pest's declarative test style.

So I assume that preferred pint preset for application own pest tests is laravel?

According to this guy
https://www.reddit.com/r/PHP_Dinos/comments/1fo515g/using_laravel_pint_to_enforce_coding_standards/

Laravel uses PSR-12 which requires adherence to PSR-1 and as I was commenting above PSR-1 is problematic with PEST style. So at this point I must assume that the laravel presets override the PSR-1 troubles to make pint work well with pest (user-mode, not for this repo)

I'm asking this not to work under Laravel projects, but WordPress projects using Pest for testing (so I must override the PEST part with a different preset for PEST other than the default WPCS which I'm not even sure if pint supports.

[pansycarrero]

The repository appears to use Laravel Pint and Rector rather than PHPCS as its primary coding-standard tools. For PEST tests, it would be best to follow the project’s existing formatting configuration instead of adding a separate PHPCS standard that could conflict with PSR-1.
Website: https://montanapestpros.us/locations/pest-control-in-great-falls