Codeception VS collision

Personal experience: - don’t use Behat unless you really needed a “story telling”, it has a intermediate layer Gherkin that you’ll need to code. You can write “Given/When/Then” steps but you’ll also need to write “php code” that will interpret this step. - using real browser be prepared for instability - any interaction with JavaScript can broken/delay execution - be prepared that this tests are call functional they are the most expensive test, so start small unit then integration and only then functional. - use https://github.com/symfony/panther or https://codeception.com/ you’ll have phpunit alike interface to run them. - you’ll need to reset state of your database each time to provide “isolation” and stability

Codeception: https://codeception.com/

I would say to check out Codeception. Codeceptions has modules for Symfony and database generally. Long and short of it is that if you want you can run api tests that go into the controllers and rollback the database afterwards.

There are enough blog posts about Jest or Cypress already, so let me introduce Codecept. It comes in two flavors. There is Codeception for PHP, and there is CodeceptJS for JavaScript which we will be using here.

There are many tools you can use for this purpose, but one I particularly like is CodeCeption. What I like most about it is that it's a unified tool that can be used to perform several types of tests, acceptance being one of them.

This is a quote from this year's new Testify T-Shirt, my physical takeway from this event. While I don't agree that we should automate everything we can, I still chose this design as it shows Codeception code.

And within the Symfony ecosystem Codeception, which “collects and shares best practices and solutions for testing PHP web applications. With a flexible set of included modules tests are easy to write, easy to use, and easy to maintain.”

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.

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.

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 :).

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.