Prophecy VS PHPUnit

Prophecy is a framework for creating test doubles that was initially built for the requirements of phpspec, but it can be used with any other PHP testing framework. Since PHPUnit 4.5 it bundles Prophecy within PHPUnit itself, but as of PHPUnit 9.x this bundling is deprecated and set to be removed in PHPUnit 10.

Recently I have been working a lot with PSR-15 and PSR-18 and one of the characteristics of these recommendations is that it uses the immutable objects specified in PSR-7. Soon after we introduced PSR-18 in our codebase a colleague implemented a client including a unit test that was passing. And yet the code was failing when run in the browser. The cause of this was that the fact that RequestInterface objects are immutable by specification was overlooked. Due to the use of Prophecy and prophesized objects we were struggling to properly test it. Until another colleague introduced me to Argument::that() that is.

PHPUnit is the de facto standard for PHP unit testing. It provides a framework for writing and running tests, helping developers quickly discover and fix errors. PHPUnit encourages developers to write testable code and adopt a test-driven development approach, resulting in higher-quality code and reduced chances of errors in production.

Before updating Api Platform, you should make sure that your Api Platform routes are fully covered by tests. You can define integration tests with PHPUnit, Behat or Pest, depending on the tool you’re most comfortable with.

PHP popular tools for testing: PHPUnit

PHPUnit: PHPUnit is a programmer-oriented testing framework for PHP. It is an instance of the xUnit architecture for unit testing frameworks. Extensions/tools: brianium/paratest: Parallel testing for PHPUnit johnkary/phpunit-speedtrap: Reports on slow-running tests in your PHPUnit test suite. robiningelbrecht/phpunit-pretty-print: Better PHPUnit CLI output with Collision roave/no-leaks: PHPUnit Plugin for detecting Memory Leaks in code and tests

We want to start migrating to Attributes because of the announcement made here that in PHPUnit 12 support for metadata in docblocks will be removed: https://github.com/sebastianbergmann/phpunit/issues/4502

PHPUnit: PHPUnit PHPUnit is a testing framework for PHP. It enables developers to write unit tests, integration tests, and functional tests to verify the correctness of their code. It offers a wide range of assertions, test runners, and mocking capabilities. Documentation: Explore PHPUnit's capabilities and learn how to write effective tests in the official documentation: PHPUnit Repository

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.

Finally we install the command line version of php (no web server is needed for this project), composer which is a package management system for PHP and PHP Unit, the testing framework of PHP.

I've been developing my own symfony bundle and I would like to share with you how I'm driving continuos integration to execute my unit tests. For testing purposes I'm using phpunit and for continous integration i've choosen github actions.

PHPUnit is a unit testing framework for PHP included with Laravel and can be used to test your application's code. It provides a set of assertions and functions for testing your code and can be used to run automated tests.