skip to main content

gerg.dev

Blog | About me

Category: Automation

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

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

Tests encode knowledge

I like collecting these little adages about testing. I didn’t come up with this one, but was reminded of it by a tweet yesterday: Lots of people (including myself) chimed in about having done this themselves in the replies. She eventually attributed the idea to Paul Grizzaffi. It’s not explicitly saying “tests encode knowledge”, but… Read more

Reconciling twitter threads and manual testing

This weekend on twitter I saw this thread from Alan Page in response to this article about why manual testing is still important. I read both several times, and was left very confused because most of what Alan wrote (as I understood it) didn’t seem to have much relationship to the article (as I understood… Read more