Category: Testing Skills
-
An Introduction to Chaos Engineering for Testers
In this post I describe how I ask what happens if this fails, throttling networks and killing pods to find out how a system actually recovers.
-
Writing a Test Approach – 5 Ws and an H
By setting out the Who, What, Where, When, Why and How of testing we can create a powerful approach to share with our teams.
-
Quality narratives are a better form of reporting
How’s dinner, is it good? You wouldn’t answer that with a percentage. In this post I set out why our test reporting should work the same way.
-
Using Colour Psychology to Test your Front End
When testing a front end it’s important to be able to understand and inform your teams on what the colours they’ve used can mean. We all know some general rules of thumb; red means danger (in the West) and yellow and black are a warning, but what else can marketing psychology tell us?
-
Exploring Non Functional Requirements by finding Low Hanging Fruit
Recently I’ve been working on more greenfield projects and have been setting my own scope on what to test and quality looks like. One of the areas of quality I’ve been exploring are the non functional areas (something I’ve not previously really gotten into) and have found some easy to get started with tools.
-
Using Triforce to define Acceptance Criteria
In this post I describe Triforce, the session I run so that every perspective a story needs is represented before anyone starts building it.
-
Continuous Testing: Creating a testable CI/CD pipeline
In this post I set out how to design tests that give a CI/CD pipeline real confidence, using service level tests and Docker networks to keep feedback fast.
-
Let’s Mindmap Test Notes
In this post I show how I use mindmaps for test notes, they make coverage visible at a glance and let people see how I explore.