Activity
Jesse Berkeley
Senior Test Engineer
Hey folks, I am Jesse Berkeley and I'm here to learn from you all as I continue to grow in the craft of test engineering and quality engineering. Looking forward to learning from the community!
Open To
Write
Podcasting
Meet at MoTaCon 2026
earned:
Book Review: Full Stack Testing
earned:
Miasma Worm Hits 73 Microsoft GitHub Repositories in Major Supply Chain Attack
contributed:
earned:
This Week in Quality
registered for:
Share your week’s highlights, challenges, and lessons in quality
earned:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
thanked contributors on:
When a system improvises like a jazz soloist, "different" stops meaning "wrong"
earned:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
awarded Demi Van Malcot for:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
awarded Adam Davis for:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
awarded James Pearce for:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
awarded Lauren Lassey for:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
awarded Oleksandr Romanov for:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
awarded Simon Tomes for:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
awarded Piotr Wicherski for:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
awarded Demi Van Malcot for:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
awarded Adam Davis for:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
awarded James Pearce for:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
awarded Lauren Lassey for:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
awarded Oleksandr Romanov for:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
awarded Simon Tomes for:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
awarded Piotr Wicherski for:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
earned:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
earned:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
earned:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
earned:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
earned:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
earned:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
earned:
What's the hardest part of defining "expected behaviour" for a system that produces different output every time?
contributed:
When a system improvises like a jazz soloist, "different" stops meaning "wrong"
awarded Ady Stokes for:
3.2.0 of MoT Software Testing Essentials Certificate
earned:
3.2.0 of MoT Software Testing Essentials Certificate
thanked contributors on:
Reflections of Clare Norman's take on workshops during TWiQ. Goals are important when running a workshop yet the way you get there is different to a meeting. People show up and participat...
earned:
Hot take: A workshop is everything a meeting is not
awarded Simon Tomes for:
Hot take: A workshop is everything a meeting is not
awarded TWiQ — This Week in Quality for:
Hot take: A workshop is everything a meeting is not
awarded Clare Norman for:
Hot take: A workshop is everything a meeting is not
earned:
This Week in Quality
earned:
This Week in Quality
registered for:
Share your week’s highlights, challenges, and lessons in quality
earned:
3.4.0 of MoT Software Testing Essentials Certificate
earned:
How would you define a guardrail?
earned:
3.4.0 of MoT Software Testing Essentials Certificate
earned:
How would you define a guardrail?
awarded Jessica Mosley for:
Quality people are truth tellers
awarded Judy Mosley for:
Quality people are truth tellers
earned:
Quality people are truth tellers
thanked contributors on:
A great conversation on friction, influence and showing up authentically
earned:
Quality people are truth tellers
awarded Jessica Mosley for:
Quality people are truth tellers
Better than a generic video, see YOUR test, live, ready to show you what matters most: quality at scale.
SmartBear's vision for using AI agents to support application integrity and software quality
With servers in >250 cities around the world, check your site for localization problems, broken GDPR banners, etc.
Is AI failing, or is it an API? Simulate your API environment in WireMock Cloud to run better tests, earlier
