Tried out a bit of #Pest today. A bit weird to write that less but get so much. I think I have to get used to this. But I see me writing more tests with Pest. Looking forward to work more with it!
"By forcing us to precisely describe the behavior of our software, property-based testing in turn forces us to make explicit not just the assumptions that we made when writing the tests, but also the assumptions that we made when writing the software. Often we will discover that those assumptions are wrong"
➥ Increment Magazine
"I often jump into the TDD flow when I’m adding a new feature to a product or confirming the existence of a bug. If it’s not clear how I should approach the problem, the best way for me to start is with a test. Tests force me to break down the problem into steps to reach an initial solution, while refactoring gets me to a cleaner solution"
➥ Increment Magazine
💡 Just realised that you can use @coveragepy not only to determine your test coverage but also to find out how much of your codebase is present in your documented examples! 😁
I have to confess to some hubris. After evaluating the various Node.js testing frameworks, I've decided to write my own instead. In this 🧵, I'll explain why. Mostly so I can remember it for the future.
@mikestreety At least one of the tools I work on uses Docker to start a local Solr database, loads 20-30 test entries into it, and then queries them through the API to make sure it works as expected. It came in handy recently when I overhauled the Solr query and left out one pattern, so all the tests found one fewer result than they expected. #testing
“Let’s build systems that are really hard to test because we’re too busy making money and will cash out before we have to pay the technical debt bill.” — 99.999% of developers
@grmpyprogrammer I think untestable systems are built by programmers that haven't learned how to test their code. It's our responsibility to teach them how to build testable systems. #testing
Fit Testing to ensure a good seal on your mask [Part 1]
This thread explains what #mask#fit#testing is (#qualitative and #quantitative), why it is important, and my testing experience with some real-world results of various types of masks including NIOSH #N95 and ear loop. 🧵 1/
I started to review the blog post requests, drafts, and ideas accumulated over time. Most topics revolve around #rex, #perl, #opensource, #gentoo, #cicd, #git, #testing, and #CLI — with some overlap.
Help me decide: which topic shall I focus on first?