Writings on various topics (mostly technical) from Oliver Hookins and Angela Collins. We currently reside in Sydney after almost a decade in Berlin, have three kids, and have far too little time to really justify having a blog.
Yet another long-overdue post. The last couple of weeks (or perhaps sprints) my team has dived into Typescript for a new project. I like it, really like it. Maybe that's just because for years I've feared Javascript, haven't understood enough about how to unit testing, and found myself writing terrible code and just running it to find the bugs. This is not a very good development methodology.
Disclaimer: Most of this post was written in 2014, but it's been languishing in my drafts folder for a long time and I thought I'd push the publish button rather than waiting to perfect it. The original context was that I was attempting to perform integration testing on a client application that needed to handle a variety of different network behaviours - including TCP resets. I mulled over how…
We have an internal service that takes requests of the form something
like /foo/{ID}/bar which basically is expected to generate data of the
form "bar" about the ID entity within the collection "foo". Real
clear! Because this service has a bunch of similar routes that have a
resource identifier as part of the request path, we use the Gorilla Mux
package. There are
a lot of different approaches to…
I'm still building up to my article on how to properly mock calls to Rake's sh to facilitate testing of your Rakefile tasks but I haven't quite worked up the strength to trace the calls through the libraries and into Eigenclass wonderland. For the moment, I've got just enough fodder to write a bit about determinism in testing.
Since Friday, both a coworker and I have been hit by the same testing…