Callum Akehurst-Ryan
Callum Akehurst-Ryan
Staff Quality Engineer
He/Him
Hi I'm Callum, a software tester and quality coach in London. I talk about exploratory testing, test strategy, diversity & inclusion and building testing in agile teams / startups.
🎂 MoTaBirthday | October 9, 2020
Open To
Speak
Write
Teach
AI isn't going to save your dysfunctional engineering team... it's going to expose its problems.With everyone rushing to hand their engineers AI agents almost no one is stopping to ask whether thei...
15 Jun
I’m excited to share that, alongside TeamMoT, we’ll be gathering 50 Leaders in Quality on September 30th.
What looks like a one-day event is actually the beginning of a bigger journey: a committ...
9 Sep
Eighteen months, 19 modules, and 59 amazing contributors later, the MoT Software Testing Essentials Certification is complete!
Looking back, my favourite part has been seeing so many community m...
18 Aug
Great to catchup with Simon and Callum at the MoT London meetup. It was the biggest one yet and a lot of people for me ha, so nice to chat with familiar faces!
And see the people enjoying their...
3 Jul
Explore shift right and how to practice it within testing
25 Feb
Discover how “good enough,” honesty, and a clear quality narrative help teams care more and make better decisions.
21 Nov
Quality Narrative
A quality narrative is about the way that we can talk about quality holistically. It's a good replacement for, say, a test report. A report usually is like a condensed view of the world that sort of tries to compress down into numbers or a graph or really salient points to go cool. Like here's your parcel fail criteria.
Like here's what we found as a result of something. Whereas a narrative is more of a communication around quality. What's the good, what's the bad, and what's the ugly? We sometimes talk about a quality narrative when we're doing debriefs and exploratory testing.
So a quality narrative is just a slightly more open, a more wider way of communicating what we what we know about something to help inform divisions and build influence on quality as well.
Quality Engineering
Quality engineering ... is very focused on influencing. Your ability to influence teams, engineers, organisations, managers, other testers, anyone. Quality engineering is about building quality into things.
Chaos Engineering
Chaos Engineering is the discipline of exploring your system to see how it handles turbulent conditions in live. It’s a term that was coined by Netflix to see whether their systems and infrastructure could handle infrastructure failures, network failures, and application failures.
Basically Chaos Engineering asks, what would happen if this thing failed?
Test design
The purpose of our test design is to help people understand what it is we're covering, what it is we're testing, and what is it they're going to find out about the system from our testing. Because we want to share that information, that useful information, to help the team understand the quality of what's being built. And the whole reason we design our tests in the first place, it's not necessarily for us. It's to share that with the rest of our team so they can help go, oh, have you thought about this? Or, hey, maybe this isn't a priority for us right now. So that's the key thing to think about there.
Test plan
Test plans can mean all sorts of different things. It could be our approach. It could be how we're testing, or it could be what we're testing. It could be a series of scenarios or a series of tests as well.
Why did testing miss this… Because you didn’t set a risk appetite
(cakehurstryan.com)
21 Jul
AI Readiness Radar: A self assessment tool for engineering teams
(cakehurstryan.com)
15 Jun