#behat — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #behat, aggregated by home.social.
-
Integration passes #PHPStan level 9, writing #Behat tests for rendering and caching is a breeze...
Next steps:
* documentation
* improved transpilation error handling
* extension point for the delegation mechanism for #NeosCMS , e.g. for the future OPGM (Object-Propery Graph-Mapper)
* transpilation from .cpx to TypeScript for isomorphic rendering
* a language server for #PHPStorm etc.
* you name it -
Testing delayed Symfony Messenger message handling with Behat. #symfony #behat
http://angelovdejan.me/2025/07/22/testing-delayed-symfony-messenger-message-handling-with-behat.html -
All software has #bugs
I made my first github commit for the #Moodle #Gapfill question type In April 2012. I have made 1,510 commits since then. This year on Feb 5 2025 Mark Johnson reported a bug in backup caused by spelling errors in field names.
https://github.com/marcusgreen/moodle-qtype_gapfill/issues/117
I have created a #behat test to reproduce the bug and a patch to fix it. It took approximately 5 hours in total.
All software has bugs, automated tests are not a luxury. -
All software has #bugs
I made my first github commit for the #Moodle #Gapfill question type In April 2012. I have made 1,510 commits since then. This year on Feb 5 2025 Mark Johnson reported a bug in backup caused by spelling errors in field names.
https://github.com/marcusgreen/moodle-qtype_gapfill/issues/117
I have created a #behat test to reproduce the bug and a patch to fix it. It took approximately 5 hours in total.
All software has bugs, automated tests are not a luxury. -
All software has #bugs
I made my first github commit for the #Moodle #Gapfill question type In April 2012. I have made 1,510 commits since then. This year on Feb 5 2025 Mark Johnson reported a bug in backup caused by spelling errors in field names.
https://github.com/marcusgreen/moodle-qtype_gapfill/issues/117
I have created a #behat test to reproduce the bug and a patch to fix it. It took approximately 5 hours in total.
All software has bugs, automated tests are not a luxury. -
All software has #bugs
I made my first github commit for the #Moodle #Gapfill question type In April 2012. I have made 1,510 commits since then. This year on Feb 5 2025 Mark Johnson reported a bug in backup caused by spelling errors in field names.
https://github.com/marcusgreen/moodle-qtype_gapfill/issues/117
I have created a #behat test to reproduce the bug and a patch to fix it. It took approximately 5 hours in total.
All software has bugs, automated tests are not a luxury. -
All software has #bugs
I made my first github commit for the #Moodle #Gapfill question type In April 2012. I have made 1,510 commits since then. This year on Feb 5 2025 Mark Johnson reported a bug in backup caused by spelling errors in field names.
https://github.com/marcusgreen/moodle-qtype_gapfill/issues/117
I have created a #behat test to reproduce the bug and a patch to fix it. It took approximately 5 hours in total.
All software has bugs, automated tests are not a luxury. -
Unused Definitions with Behat Static Analysis. #behat #PHP
https://tomasvotruba.com/blog/unused-definitions-with-behat-static-analysis -
Testing #Moodle code with #behat is easier with docker. The latest versions includes No VNC so you can view the output via the browser, removing the need for a separate VNC client.
I used this docker compose file
version: '2'
services:
chrome:
image: selenium/standalone-chrome:4.22.0-20240621
ports:
- "7900:7900"
- "4444:4444"
volumes:
- /dev/shm:/dev/shm -
I was doing some #Moodle #behat #test code #development. I right clicked to create a file, gave the file a name and the file opened. The MDL_code plugin kicked in (it saw the .feature extension) and generated some context specific boilerplate code at the top of the file.
This is what development should be like, the machine can do the plumbing, the developer can do the creating.
https://mdlcode.dev -
On may 14 we have a new #meetup in #Eindhoven , We have @timobakx to speak about testing API endpoints using #Behat and #Gherkin Possibly a must-attend event if you develop APIs... ;)
For more information and RSVP: https://www.meetup.com/php-laravel-eindhoven/events/300028573/
-
We use the Alice bundle for our fixtures in the behat feature tests. With the last update the order of the inserts of the entities has been changed. I don’t know how or why but it was done. But we must ensure that the entities has the expected ids.
Now we change to the Foundry package where we can be safe that the entities will be created in the expected order.
Does someone had the same problem with the Alice bundle?
-
@ocramius I just had a discussion about #Playwright vs #Behat for E2E tests, any opinion on that?
-
New blog post : "Writing a custom Behat formatter"
#php #behathttps://julien.deniau.me/posts/2024-01-24-custom-behat-formatter
-
I had a great time participating in the 2nd WP-CLI Hack Day today.
I’ve been a longtime advocate for the tool, so it felt great to spend some time learning its internals and contributing some code to it.
It was also my first time writing #Behat tests, which kinda feels like magic.
https://make.wordpress.org/cli/2023/11/11/twenty-one-merged-prs-for-wp-cli-hack-day-2023/
-
@grmpyprogrammer Playwright is on my list end-to-end testing tools to try out.
I most recently used Selenium+Dusk but it was painfully slow. Playwright looks like an intriguing alternative to Selenium.
@zaherg and I talked about it a bit a while back, but wasn’t sure how easily you could drive it with #PHP.
Looks like there may be workable #Behat drivers, so maybe it has better PHP support now?
-
Behat: The Easy and Effective Way to Write Acceptance Tests via Jaroslaw Szutkowski.
https://dev.to/jszutkowski/behat-the-easy-and-effective-way-to-write-acceptance-tests-cm4 #Behat #PHP :php: -
If you're using #Cucumber (or #Behat or #Behave or #SpecFlow or #GoDog etc.) for #agile #testing, please fill out this very quick survey:
https://www.surveymonkey.com/r/KFLWZVQ
It's designed to help us validate some assumptions about our users.
Please share it with your friends, colleagues and clients!
-
Am currently neck deep in test fixture dependency hell and it's horrible.
The only way to figure out what I've done to break each of these 6 tests is to manually step debug each one to see what fixture is bad.