Illiteration – Testing times in Software Testing

Continuing my posts on strategy, here’s a new example outline of how I’ve recently approached test strategy for larger, traditional organisations, transititioning to DevOps. It contains a lot of items that would be aspirational for some places, but also creates a view of something quite achievable that fits with typical change management systems you’ll find […]

In a recent Twitter interaction, I was pushing Alan Page to clarify a key poing on his anti-UI-automation thread. I didn’t get it, and there have been a few more responses such that I wanted to make my current thinking and position clear. I tweeted this as well, but here’s the thread for those not […]

This blog post regarding test code being harder than application code was passed around the office, and I thought I would preserve my response here. You’ll need to read it first for this to make much sense. I think there’s a reasonable point that testing is frequently trivialised, but I don’t think saying that the […]

I’m surprised at how relevant it all still is, but I have added something that I think is missing that I’ve learned in my last couple of roles. See my ‘Essence of Agile’ Haiku for the update.

Alister Scott‘s post on Incrementation vs Iteration was doing the rounds at work with some comments, and I felt the need to comment.  I had a couple of attempts at responding to this.  It’s a big topic, but to some degree I think iterative vs incremental is a bit of a distraction as a general […]

Instant sequence of New South Wales licence plates: start_lpn=”AA00AA” end_lpn=”ZZ99ZZ” return start_lpn.upto(end_lpn).collect { | lpn | lpn }

Cem Kaner’s interview on the uTest blog talks mostly about his new book, but was especially interesting when it got to the part about emerging trends. <Scientific> communities are sometimes characterized as moving between two dysfunctional extremes, with stagnation at one end and fragmentation at the other. In the stagnant extreme, everyone pretends to believe […]

I currently have a vacancy in my team for an assistant test lead to carry some of the low-level planning, bug and environment management load.  They would also be hands-on. See Transurban’s career site for details or contact me if you have questions.

I don’t know if it is, but I enjoyed Michael‘s post on problematic uses of ‘should’ in requirements.  Enjoy.