Tag: test coverage
Bad reasons to test
“Complete” testing is impossible, so we have to do the best we can with the time and resources we have. Often, that comes down to making sure that there’s a good reason for each test to exist. If there isn’t, then you should remove it and spend that time on something more valuable. When evaluating… Read more
What should the ratio of automated to exploratory testing be?
I popped into an online panel about testing today, and a question along these lines was asked: what is the ratio between automated testing and exploratory testing at your company? I get the gist of what is being asked here of course, and wouldn’t get too pedantic in answering it in the moment, but this… Read more
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 with rules like “don’t commit any code with less than 80% coverage”. However, it is also an easy metric to manipulate, and doesn’t necessarily prove anything about the quality of the tests… 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
Emergent complexity from simple specs with Hive
Even the simplest specifications, when combined, can give rise to complex behavior and unexpected edge cases. This is the mechanic that both makes testers’ work challenging and board games fun. The game Hive is a great example of this (I recommend the pocket edition). It seemed like a fun exercise to look at each piece,… Read more