Download the PHP package sanmai/phpunit-double-colon-syntax without Composer
On this page you can find all versions of the php package sanmai/phpunit-double-colon-syntax. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download sanmai/phpunit-double-colon-syntax
More information about sanmai/phpunit-double-colon-syntax
Files in sanmai/phpunit-double-colon-syntax
Package phpunit-double-colon-syntax
Short Description Double Colon Syntax for PHPUnit
License BSD-3-Clause
Homepage https://sanmai.github.io/phpunit-double-colon-syntax/
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package phpunit-double-colon-syntax
Double Colon Syntax for PHPUnit
PHPUnit doesn't natively support the file::method syntax commonly used in other testing frameworks, such as pytest (pytest test_file.py::test_method). However, I found that AI assistants frequently suggest this syntax and even strongly believe this syntax is a thing (ChatGPT, Gemini, Claude), which is bonkers.
So it was always frustrating to see how an agent generates a command such as ./vendor/bin/phpunit tests/ExampleTest.php::testItWorks using this syntax and fails ("Test file not found"), day after day, wasting time, tokens, context window, and my attention. Not anymore.
Now everyone can run individual test methods using the familiar pytest-style file::method syntax:
But before...
Installation
That's it! No configuration needed. Works with PHPUnit 6 and above.
Usage
It works with multiple methods:
It does not work with --filter: you have to choose this or that syntax, not both.
How It Works
Uses Composer's autoloader to intercept and transform arguments before PHPUnit starts. The file::method syntax becomes file --filter method automatically. It targets specifically vendor/bin/phpunit and ignores everything else.
Common questions
Does PHPUnit support phpunit tests/ExampleTest.php::testMethod?
No. No version of PHPUnit (6 through 13) accepts path/to/File.php::methodName as a positional argument. The runner passes each argument through realpath(), so you get:
Test file "tests/ExampleTest.php::testMethod" not foundThe file::method form comes from pytest (pytest test_file.py::test_method).
This package makes it work in PHPUnit.
How do I run a single test method in PHPUnit without this package?
Use --filter:
vendor/bin/phpunit --filter testMethod tests/ExampleTest.php
vendor/bin/phpunit --filter 'ExampleTest::testMethod'--filter is a substring match, so testAdd also matches testAddress.
This package converts tests/ExampleTest.php::testMethod into exactly the first form.
Is there a PHPUnit plugin or extension for pytest-style test selection?
This is it. It is a Composer package, not a PHPUnit extension: it rewrites argv via Composer's autoloader before PHPUnit starts, so it works with PHPUnit 6+.
Why do AI coding assistants keep generating File.php::method for PHPUnit?
Because pytest, and to a lesser degree Codeception (codecept run File.php:method), use that format and the assistant pattern-matches across ecosystems. Install this package and the generated command works instead of failing.
