phpunit-pretty-print
collision
phpunit-pretty-print | collision | |
---|---|---|
3 | 4 | |
62 | 4,436 | |
- | - | |
7.4 | 7.8 | |
3 months ago | 13 days ago | |
PHP | PHP | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
phpunit-pretty-print
-
PHP libraries and tools
robiningelbrecht/phpunit-pretty-print: Better PHPUnit CLI output with Collision
-
I created a PHPUnit 10 extension to prettify CLI output
When 99% of the bytes of the actual code of your package is "fun" (see Quotes.php in the /src dir, my opinion on the quality of the other 1% of bytes of code will detoriate.
collision
-
I created a PHPUnit 10 extension to prettify CLI output
I really like how Pest PHP formats and outputs test results, but I still prefer to use PHPUnit. Luckily there's Collision. This package is designed to give you beautiful error reporting when interacting with your app through the command line.
-
what are you using to make phpunit output pretty?
I like collision https://github.com/nunomaduro/collision it is the output formatter wich the Pest Testing Framework is also using, I'm using it without Pest.
-
PHPUnit, do i need to learn it?
It was as I know just released 2 years ago. And as I know Nuno already works on PestPHP 2.0. It is also build on top of PHPUnit which means you can run all PHPUnit tests also with PestPHP runner. It is mostly be used in Laravel ecosystem as the maintainer is a maintainer of Laravel, I personally did not yet give it a try as I'm more in the Symfony world, but I use mostly the same PHPUnit Printer called Collision which make the PHPUnit a bit nicer :).
-
Announcing x-ray
I also felt from the beginning that the code snippets should be syntax highlighted in the console output. After a decent attempt at creating basic syntax highlighting, I again went with the tried-and-true method of extracting existing code from a project. In this case, the original source code came from nunomaduro/collision. Again, with some modifications, it suited my needs perfectly.
What are some alternatives?
PHPUnit - The PHP Unit Testing framework.
awesome-copycats - Awesome WM themes
Pest - Pest is an elegant PHP testing Framework with a focus on simplicity, meticulously designed to bring back the joy of testing in PHP.
termwind - 🍃 In short, it's like Tailwind CSS, but for the PHP command-line applications.
phpunit-coverage-tools - A PHPUnit 10 extension to enforce minimum code coverage by using the clover XML report
ray - Debug with Ray to fix problems faster
Psalm - A static analysis tool for finding errors in PHP applications
PHP Mess Detector - PHPMD is a spin-off project of PHP Depend and aims to be a PHP equivalent of the well known Java tool PMD. PHPMD can be seen as an user friendly frontend application for the raw metrics stream measured by PHP Depend.
tlint - Tighten linter for Laravel conventions.
Infection - PHP Mutation Testing library
Codeception - Full-stack testing PHP framework