💡 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.
In these times, the benefits of writing unit tests are huge. I think that most of the recently started projects contain any unit tests. In enterprise applications with a lot of business logic, unit tests are the most important tests, because they are fast and can us instantly assure that our implementation is correct.
“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
@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
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?
Nullables are a novel approach to testing that allow you to create fast, reliable tests without using mocks (or interfaces). They're a way of "turning off" production code so you can have sociable, state-based tests that don't talk to the outside world.
I'm hosting office hours on May 10th at 9am Pacific / 12pm Eastern / 18:00 CEST for anybody who'd like to discuss these ideas. Bring your code! Details and a calendar reminder are available here: https://www.jamesshore.com/v2/calendar/2023-05-10
Now that #AI can write #code I think the smart career move is to get into #softwareTesting; defining success in a problem space was always the hard part of #softwareDevelopment and will need even better tools now!
@ChristosArgyrop@bentomn@kyleha@cubic_logic Agreed, poor internal docs are rampant regardless of language, in stark comparison to the #OpenSource#Perl libraries on #CPAN. So much there is well-documented and -tested and the culture encourages continuous improvement.
Perl #developers that turn a blind eye to CPAN are doubly handicapped: they (poorly) reinvent the wheel and miss exemplars of good #documentation and #testing.
Unit testing tips by examples in PHP (github.com)
In these times, the benefits of writing unit tests are huge. I think that most of the recently started projects contain any unit tests. In enterprise applications with a lot of business logic, unit tests are the most important tests, because they are fast and can us instantly assure that our implementation is correct.