Software Testing

TLDR; Comparing implementations is not done to criticise, it is done to learn, and understand that different motivations and end goals create different code. Different models of the application, lead to different code. The programmer implements models of the domain, and behaviour, as code.

TLDR; Every approach to automating has risks, issues and benefits. Often we don’t think these through. When we do we will see that automating has a different set of answers than automating strategically. This helps reinforce the difference, without having to stick to definitions.

In my conference talks and on my blog I make a distinction between Automating Tactically and Strategically. In this blog post I will conduct an exercise to look at the benefits, risks and issues associated with a particular example of automating tactically.

TLDR; I automated the unchecking of all Twitter Interests using simple JavaScript at the console. I explain the code I wrote, and how I wrote it to act as a case study in Tactical Automation.

Twitter Interests have been automatically collated. You can manually review and amend these (there might be hundreds). I decided to uncheck them all. And did so automatically.