I recently found myself writing some integration tests (or whatever you'd like to call them, people will argue about terminology for hours) for an app. Anonymous classes made testing the real implementation of my interface really easy, here's how.
Here's a super-quick way of using the Symfony Process Component in Behat Contexts to run processes in the background.
I've been porting across one of the live demos I do (that's a Symfony project to demonstrate BDD & Behat stuff) from the built-in PHP web-server and a locally-hosted MySQL Database to a Docker configuration. I had some struggles with getting my Web UI Behat suite to work correctly inside the PHP container, here's what should be done.
While giving my BDD & Behat talk recently, I was asked an interesting question by a tester about how to avoid writing implementation in feature files.
With less than 24 hours until Hack24, I've been grabbing the stuff I need (well, probably don't need...) so I have everything sorted and can leave early in the morning.