A demonstration of Mutation Testing
Test coverage is one of the simplest possible metrics to help gauge quality of testing, which makes it one that is often targeted (don’t commit any code with less than 80% coverage) and potentially gamed. A lot of people dismiss it entirely for those reasons. While there is a good defence to be made for… Read more
Five highlights from AssertJS 2019
AssertJS, a conference specifically about testing in JavaScript, took place in Toronto last week. Interestingly, I’d say most of the talks were not specific to JS at all. Here are my top 5 highlights, in no particular order: 1. Tophatting From Adam Archer: “Tophatting” is the a word used at Shopify that refers to actually… Read more
Eleusis: A card game for testers
This game was originally invented in 1956 and improved in the 70s by Robert Abbott, but I came across it this week through the game review site Shut Up and Sit Down. When I watched that video, I immediately recognized it as a cousin to both The Dice Game and Zendo, because of its use… Read more
The first Ministry of Testing meetup in Toronto
Last week I organized the first meetup in Toronto under the banner of the Ministry of Testing. There have been tester meetups in the city before, but they tended to be infrequent and or short-lived, with the event I was aware of almost a year ago. With Toronto as a fast growing tech hub, with… Read more
What you’re saying in a commit without tests
A corollary to last week’s post: A commit without a test can effectively be read as “It would be okay if somebody undid this, even unintentionally.” Sometimes that’s actually what you want; it might be inconsequential or a rapidly changing aspect or some internal implementation detail. You might be saying “this doesn’t directly impact the… Read more