Testing

TLDR; Automating is not limited to “Test Automation”. With the ability to code, we gain the flexibility to approach problems in multiple ways. We can refactor tactical code to become strategic code.

I needed to migrate some data from one system to another. To do it manually would have taken me about 1.5 to 2 days. I automated tactically and was done in 2 hours.

TLDR; Any time you see a list of pros and cons on the internet and ‘believe’ the pro or con, ask yourself “But What if…?”

I see a lot of pro and con posts and questions on the internet. They lack the context behind the pro and con identification, so I find it hard to use them directly.

This is a test report on the testing I performed after migrating my blogs on 28th December 2018, from 14:00 - 18:26.

TLDR: Firefox now lets us Edit and Amend requests in the network tab, for other browsers we can convert to cURL or fetch (or use a proxy)

TLDR; Imagine never having to worry about saying “Verification” when you meant “Validation”. Well you can. Write down what the V-words imply, and then use those sentences you wrote down instead.

TLDR: Do you ever ask yourself rhetorical questions? If so, try and answer them by building assumptions. Then investigate your assumptions.

Do you ask yourself rhetorical questions?

I suspect most people do.

Leaving them unanswered means not following up on a opportunity for learning that your brain has put in front of you.

TLDR: Rather than discuss ROI in depth, I want to explore how to evaluate ROI for yourself, so I provide some questions as an exercise e.g. “Why do you use ROI?”, “What do you gain?”, “What do you lose?”, etc.

I am often asked about ROI. And I wrote a parody answer. In this post I explore initial beliefs and then questions to explore and expand my model of ROI.

TLDR: If you want to invest in yourself, we have books and courses and a patreon page

Finding testing too expensive?

Trying to replace your testers by Automating Testing?

You’re doing it wrong.

Tool vendors want to sell you tools to automate your testing and make testing cheaper - but here’s what they don’t tell you.

TLDR; Testing driven by technical understanding seeks to observe at multiple levels of the application stack and the testing conducted is informed by identifying risks in a model built by observing the application below the GUI.

I created a short live exploratory testing video using Orange HRM

The video is on YouTube and ad free via Patreon (along with many more exclusive videos and content).

TLDR; Notes on Shift Left, where I try to explain why I don’t use the term and what I use instead. Evolve, Grow and Improve rather than Shift and Move

For some reason I’ve had a few emails and linkedin questions asking me what I think about “Shift Left”. I thought I’d put out a public answer.

I’ll start with - I do not use the term “Shift Left” because:

• It seems like “consultant speak” and, while I’m a consultant, I try to speak clearly
• It obscures, rather than clarifies, whatever point it is trying to make
• It makes me think of ‘moving a whole thing’ rather than improving the System

Instead I think of supporting the growth and evolution of a System over its lifetime and I don’t need “Shift Left” to do that.