You need to sign in or sign up before continuing.
Neil Taylor
Neil Taylor
Lead Quality Engineer
I've been testing for 20+ years with experience in Exploratory Testing and tools such as CI/CD, Bruno and Postman. I'm a self-taught pianist and enjoy writing and recording my own music.
🎂 MoTaBirthday | April 10, 2015
Open To
Meet at MoTaCon 2026
Write
Podcasting
Great to see Stuart Thomas on stage.So many interesting thoughts and ideas coming from his talk.Centre to his talk he is explaining the “5 shifts of testing ai”.
1 Oct
Loving the intros from Gwen and verlle, the caption system is rather cool and loving the appearance of Bug!Also cool 99 talk from Paul from Wonderproxy and Rosie talking about community as a service.
1 Oct
The very first talk at Leading With Quality Today was an interactive session where Stu Day talked about Storytelling and Bringing quality to live. I really enjoyed his session and the various...
30 Sep
Build team resilience as colleagues leave and your team's knowledge changes shape
24 Aug
Sometimes the most effective guardrail isn't the most sophisticated one
21 May
A warm pre-MoTaCon episode full of conference anticipation, community stories, practical advice for first-time attendees, and excitement around stars, selfies, Moments, meetups, and merch.
25 Sep
A lively episode about MoTaverse profile upgrades, MoTaCon momentum, AI-assisted testing, hidden knowledge silos, and why real human conversations still matter when tools move fast.
7 Aug
Comments
(15)
Journey Through the Stars
Thank-you for your very kind and supportive comments.
Thank you to the MoTaverse Community
Bug Congrats Gary! Look forward to hearing all about your new role on a future TWiQ episode!
Call for Insights turns 45
Bug Congrats Simon!
It was a pleasure to be one of the first to have the chance to contribute to your new idea! 😀
Friction has a complex relationship with quality
Thank you both for sharing your conversation. The whole topic of the friction that can restrict and holds us back within a development team is definately worth exploring more. For me the biggest challenges I find are around the cognitive impact of too much context switching, managing conflicting priorities and getting a good balance between helping people and knowledge sharing.
Exploring My Reports
Thank you for sharing this Adam.
Some while ago I moved to recording testing sessions using VS Code and Markdown format (I like it as it works quite easily for screenshots and console output) and I've never quite settled on the categories to include in my report. I have to say I wasn't aware there was a Mark-map plug - but it gives a nice visual representation of the session! Also I like the way your template groups the findings.
Not registered for any upcoming events
