Pedantry

Naming things is difficult. We know that. But if you get it wrong, it can taint your whole product - at least, for pedants like me.

Today, I was investigating JavaScript Rest API testing frameworks. There seem to be two big names: Chakram and Frisby, or its newer fork IcedFrisby.

Chakram has a less silly name. It has a nice logo. Its documentation looks slicker. It appears more mature (IcedFrisby 1.0 is just 5 days old, as I write, and 1.1 is out already). The two frameworks seem to have much the same features, and I can live with the syntax either way.

expect(response).to.have.status(200);
Nice.

expect(response).not.to.be.encoded.with.gzip;
Cute.

expect(response).to.comprise.of.json({
NO. I AM NOT TYPING THAT.

It’s the sort of thing we get obsessive about.

I know, this stuff isn’t important. It’s not really English anyway, it’s machine instructions, and the parser doesn’t care, and for someone who doesn’t speak English the whole of JavaScript is just arbitrary symbols…

And I’m pretty sure the .of does absolutely nothing, and could be left out, or replaced with any number of filler words, like “.to.be.is.to.have.and.to.have.is.to.be”…

But I choose IcedFrisby.