Like so many aspects of CI, test coverage reporting is something that really ought to be set-it-and-forget-it. Of course, “forget it” inevitably comes to bite you in the ass unless you write the details down somewhere. This post is not intended to be a comprehensive guide to configuring test coverage. Instead, it’s a reminder to myself of various extremely similarly named test coverage tools, both within Rust and in the wider programming ecosystem.

Recently I’ve been dabbling in Rust. This post is an attempt to collect my thoughts on the language and toolchain, particularly for working on smallish hobby projects. These points are likely obvious to Rust evangelists. Context At my day job, I find myself mostly programming in Python and TypeScript, along with a bit of Ruby and Go. Away from work, I’m enamored with functional programming, but I don’t find strict functional code particularly natural to write for most of my use cases.