Wanted to get some low hanging fruit tickets done for Questlog. Well I also decided to create more robust testing and now I finished the first task after 3 minutes and fighting Pest for 27 minutes now.
Why in all seven hells is Game::factory()->count(5)->create(); not creating 5 games? It's always 2 or 3. Never 5. This is absolutely infuriating…
I just wanted to get my list shorter and don't break stuff while I do.
The fun part? Also creating all 5 games manually fails. Without any log or something like that…
Oof. This was a really stupid error… My factory generated games with different categories. Main Game, DLC/AddOn and Expansion.
But the view I was testing filtered games by Main Game only… So by chance it was extremely unlikely that every game is a Main Game and so the count never was 5.
Gargh, I got really used to Laravel Dusk letting me write super simple browser testing tests with #phpunit / #pest but now I need that kinda test in a non-Laravel #php project.
And to start of Monday, we have "This database engine does not support fulltext search operations.” when running local tests in sqlite, even though we have verified that fts5 is enabled.
"One NOPD veteran, speaking anonymously, said the headquarters building has been infested with vermin for his nearly two decades on the force" #rats#pest#police#NOLA#NewOrleans
I recently ran into an issue with a flaky test in our CI process. Most of the time, it would pass, but when it failed, it meant running all the tests again and hoping it would pass on the next try. When I was finally fed up enough with the waiting, I...
Using Pest to run tests on your Laravel/Livewire site? Do you get the dreaded “Latest compiled component path not found” error? To help find the real error, add $this->withoutExceptionHandling(); to your test method. You should now see the actual error causing the issue.
Vorgestern - das habe ich bisher unterschlagen - gab es zweite neue Spiel, was ich diese Woche gespielt habe. #Brettspiele habe ich bisher gekauft, wenn es sie irgendwo gab. Dies ist der erste an mich ausgelieferte Crowdfunding-Projekt. Es ist das Spiel #Pest, bei dem man einen Pestdoktor durch ein fiktives Mittelalterland bewegt, um Pestkranke einzusammeln. Das Spiel kann mit einem oder bis zu 5 Personen das Spiel spielen. Wir haben es mit 5 getan - nie wieder! 1/6 @board@brettspiele
Any #WordPress folks using #pest to do feature testing of #WooCommerce subscriptions and memberships features and cart/checkout/account workflows? Looking for examples.
I just wrote a script to use GraphViz to visualise the dependencies of one of my composer-based #PHP projects, and now I’m wishing I hadn't #sbom#nightmare
to be fair, this includes loads of development dependencies like #phpstan, #pest etc. But even with those omitted, the graph is far larger than the handful of dependencies in composer.json would suggest.
Are there examples of getting pretty output from #phpunit for custom assertions?
Projects like #Pest prove you can do a lot with phpunit’s output. I’m hoping it doesn’t take that much work to hook into correctly displaying information when an assertion fails, though.
So, two questions:
If I write a custom assertion, can I be creative with how failures display?
Can I hook into the built-in assertions and conditionally tweak their display?
Anyone have an idea what is digging divots in our front lawn? These holes are everywhere. It looks like a dog did it, but it's only our front yard, no neighboring yards. Back yard is unaffected. The strip on the other side of the driveway is also untouched. #lawn#gardening#pest
Fix Flaky Tests with Pest Repeat (seankegel.com)
I recently ran into an issue with a flaky test in our CI process. Most of the time, it would pass, but when it failed, it meant running all the tests again and hoping it would pass on the next try. When I was finally fed up enough with the waiting, I...
"Century Pest Control: A Legacy of Pest-Free Living"