Software Testing and Development Blog Posts

Subscribe to the full blog feed using RSS

All Posts | Categories | Archive

How and Why to use Variation in Testing

How and Why to use Variation in Software Testing

5 minute read - Test Automation

TLDR; Variation is a useful tactic to apply to Software Testing. Often this is random variation within an equivalence class. We can also vary when performing Exploratory Testing. Consider varying order, data, state, timing.

I found what looks like a potential bug in LinkedIn regarding the hastag processing, and it made me think through how applying a Variation tactic could help.


SauceCon 2020 Tactical vs Strategic

SauceCon 2020 Tactical vs Strategic

4 minute read - Conference

Live Recording with Q&A

SauceCon 2020

SauceCon 2020 was moved online as a free conference.

Title: Automating Tactically and Strategically

One of the biggest concepts that has made a difference to my programming and automating is the concept of “Tactical Vs Strategic”. Tactical being for a specific purpose, possibly a bit rough around the edges, not necessarily completely robust for everyone, etc.. And Strategic being critical to long term aims, maintained and maintainable, etc. In this talk I will provide examples of both strategic and tactical automating for activities as diverse as supporting testing, marketing and general life. We will also consider how and when to move from automating tactically to strategically. And how the concept has helped me change my programming style and how I write code.


Virtuoso Webinar - The Future of Testing

Virtuoso Webinar - The Future of Testing

1 minute read - Webinars Conference

Virtuoso Webinar April 2020

On 28th April 2020, I presented in a Webinar with Joe Colantonio.

The webinar was sponsored by Virtuoso.qa

I provided a short presentation on how testing will change in short and long term. And then there was a Q&A session between Adil Mohammed, Joe Colantonio and myself.

You can sign up to watch the live webinar recording with full Q&A using this link.

You can also read a summary of the webinar on the Virtuoso.qa blog


How to assess coverage of automation?

Automation Coverage

6 minute read - Test Automation

TLDR; Coverage requires some sort of model. We can organise code to support review against a mental model, and some models are executable. Other models we compare against the output of execution.

I was asked a series of questions: How can we document what an automated test does and covers without adding a lot of overhead? How do we know what is not covered by automation?