Richard Adams
Senior Test Analyst
He / Him
I am Open to Teach, Speak, Podcasting, Write, Meet at MoTaCon 2026

Passionate about quality & testing. Creator of Threat Agents card game and regularly found chatting cyber security.

Chapter Lead

Achievements

TestBash Trailblazer
Bio Builder
Avid Reader
Career Champion
Club Explorer
Article Maven
MoT Community Certificate
MoT Software Testing Essentials Certificate
Scholarship Hero
TestBash Speaker
99 Second Speaker
Chapter Lead
MoT Streak
In the Loop
MoT Inked
404 Talk (Not) Found
Bug Finder
Collection Curator
Glossary Contributor
Photo Historian
TestBash Brighton 2025 Attendee
TestBash Brighton 2024 Attendee
Cert Shaper
Course creator
Author Debut
A software tester's guide to Chrome DevTools
Introduction to modern testing
99 and Counting
Chapter Event Speaker
Inclusive Companion
Social Connector
Open to Opportunities
Found at 404
Picture Perfect
Leading with Quality 2025 Attendee
Kind Click
Supportive Clicker
Encouragement Giver
Goal Setter
Chapter Discovery
Moment Maker
Chapter Event Host

Certificates

MoT Software Testing Essentials Certificate image
  • Richard Adams's profile image
Awarded for: Passing the exam with a score of 100%
MoT Community Certificate image
  • Richard Adams's profile image
Awarded for: Achieving one or more Community Stars in five or more unique months

Activity

16.6.0 of MoT Software Testing Essentials Certificate image
16.6.0 of MoT Software Testing Essentials Certificate
Two ways to use the “5 whys” method: Root cause of bugs and identifying continuous improvements image
Two ways to use the “5 whys” method: Root cause of bugs and identifying continuous improvements
Two ways to use the “5 whys” method: Root cause of bugs and identifying continuous improvements image
Two ways to use the “5 whys” method: Root cause of bugs and identifying continuous improvements
Two ways to use the “5 whys” method: Root cause of bugs and identifying continuous improvements image
Two ways to use the “5 whys” method: Root cause of bugs and identifying continuous improvements
Two ways to use the “5 whys” method: Root cause of bugs and identifying continuous improvements image
Two ways to use the “5 whys” method: Root cause of bugs and identifying continuous improvements

Contributions

Two ways to use the “5 whys” method: Root cause of bugs and identifying continuous improvements image
  • Richard Adams's profile image
  • Emily O'Connor's profile image
Apply the "5 Whys" technique to both technical debugging and organisational workflows to uncover deep-seated root causes and implement sustainable continuous improvements.
Lots of one snack, mix two snacks or sample a full bowl of snacks? image
  • Richard Adams's profile image
Rich Adams asks:Would you prefer to eat a lot of one snack at one, seeing how two snacks mix together or sampling the full bowl of snacks? I'm a big fan of pair-wise testing... sorry I mean pairin...
AMA Leadership Answer - How do you lead if your position has no authority? image
  • Richard Adams's profile image
So Richards question in full was "My biggest challenge when I was in a leadership role was that it wasn't a position of authority. Whilst I was the leader on how to think about quality and testing,...
How do you engage stakeholders, such as devs & product, with the findings from your exploratory testing session? image
  • Richard Adams's profile image
Richard Adams asks: How do you engage stakeholders, such as devs & product, with the findings from your exploratory testing session? Things that I've found helpful: Establishing an agreement th...
Ministry of Testing Edinburgh chapter meet up image
  • Richard Adams's profile image
  • Daniel Mcfarline's profile image
  • Arnab Purakayestha's profile image
  • Simon's profile image
  • MoT Edinburgh's profile image
  • Luca Santarelli's profile image
  • Babu's profile image
We met in a nice (albeit a bit loud) pub in Edinburgh to chat testing, careers and life in general, getting to know people in our local area.We also had a few rounds of Would Heu-Risk It, sparking ...
Rewind to my first in person event  image
  • Alan Page's profile image
  • David Christiansen's profile image
  • MoT Edinburgh's profile image
With recent excitement about Chapters, it got me thinking of the first time I ever went to an in person testing event. I had only just switched back from development to test and wanted to engage wi...
Sketchnoting "Beyond the titles: leading change as an individual contributor" image
  • Richard Adams's profile image
  • Barry Ehigiator's profile image
I was overdue doing some sketch-noting and decided to go with a talk I'd seen but was keen to see again. At MoTaCon 2025 Barry Ehigiator delivered a fantastic talk called "Beyond the titles: leadin...
Escalation image
  • Richard Adams's profile image
An issue reported by a customer to the support team that requires involvement from the engineering team. This may be because the issue is a defect or require deeper diagnosis & analysis by engineers (developers or tester) to understand the behaviour that the customer is experiencing and advise them on steps to resolve their problem. Companies often have policies or Service Level Agreements (SLAs) that define how quickly engineering teams must respond to and resolve escalations from customers.
2026 Goals - Progress already! image
  • Richard Adams's profile image
  • Bug's profile image
My first goal for 2026 was to get certified. I have taken my STEC exam, albeit with a couple of lessons to complete, and passed. Pretty darn delighted and my CV is already updated ready for some jo...
Login or sign up to create your own MoT page.
Subscribe to our newsletter
We'll keep you up to date on all the testing trends.