Behat now gives you more control over how file paths appear in test results: print absolute or relative paths, strip unwanted prefixes, and add an editor URL so paths become clickable and open directly in your IDE.
If you or your company relies on Behat, please help keep it moving forward—sponsor its maintainers and support ongoing development. https://t.co/8N195ALdnJ
Behat now includes a new formatter that outputs test results as JSON—the lingua franca of modern tooling. This powers the new Behat MCP server, enabling AI tools to run Behat tests: https://t.co/1cYKvvlfnR
Behat now fully supports PHP Attributes for defining steps, hooks, and transformations. Annotations are no longer recommended and will be removed in Behat 4. Use Rector to automatically convert your existing annotations to attributes.
Behat now supports PHP config files, replacing YAML for enhanced IDE auto-completion and improved static analysis with tools like PHPStan and Rector. Run `behat --convert-config` to give it a go today!
Since October 2024, Behat's new maintainer team has been on a roll, launching numerous releases, squashing bugs, and packing in exciting new features. Stick around—there's plenty to share in the coming days!
Today is the day @BehatPHP started to require PHP ^7.2 and Symfony ^4.4|^5.0. If one wants to help, I'd appreciate taking care of compatibility layers for old PHP/Symfony versions that are not needed anymore after this change. https://t.co/sTbTWZKVFM
Another day, another release. @BehatPHP v3.7.0 bringing back support for PHP 5.3/5.4 and introducing it for PHP 7.4. Container-interop package made optional. Next minor release will drop support for PHP <7.2 and Symfony <4.4. https://t.co/A00iYYiMtl
Eager to use @BehatPHP in your @symfony 5 application? The latest release of FriendsOfBehat's SymfonyExtension comes to the rescue! Symfony 5 and PHP 7.4 support, better Mink and BrowserKit integrations and a few more improvements included. https://t.co/yYRH9J2knh
We focus so much on tools. Especially in testing. @codeception vs @BehatPHP vs @phpunit but really why test code? To make sure it works. So don’t obsess over what tool offers the most but what process enables communication. Talk to the client and then let’s talk tooling :)
For the last few months, I have been working on my master thesis project. It may be a useful example of usage of a few concepts and libraries. What is inside? @neo4j, @symfony, #cqrs, @prooph_software, @BehatPHP & @PhpSpec Check it out: https://t.co/D2kqvaVVKY
I'll be delivering my new "BDD In Practice" workshop covering @BehatPHP, @phpunit, @PhpSpec, and how to put it all together at #phpuk17 in Feb - hope to see you there! https://t.co/s89G9VPbdl