Jesse Berkeley
Senior Test Engineer
I am Open to Write, Podcasting
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!
Achievements
Certificates
Awarded for:
Achieving 5 or more Community Star badges
Activity
earned:
3.4.0 of MoT Software Testing Essentials Certificate
earned:
Jesse Berkeley - 99 Second Community Journey
contributed:
What happens when you have 99 seconds to look at someone's MoT profile?
earned:
Quality people.
awarded Ady Stokes for:
1.0.0 of MoT Software Testing Essentials Certificate
Contributions
What happens when you have 99 seconds to look at someone's MoT profile?
A handler is a piece of code that responds to something happening — like a message arriving, a request being made, or an event being triggered.Think of it like a receptionist at an office:
Someone walks in (an event or message).
The receptionist (the handler) decides what to do — maybe call someone, give directions, or log the visit.
When something happens — for example, a user clicks a button, a message arrives, or a request comes to a web server — the system passes that “event” to the right handler, which knows what to do next.In software, a handler does the same:
It receives input (like an API request or a message from a queue).
It processes that input — maybe by saving data, calling another service, or sending a response.
As a tester, you might encounter handlers in:
APIs: A handler processes incoming HTTP requests (e.g., GET or POST).
Message-based systems (like NServiceBus): A handler processes messages sent between services.
AnalogyImagine a smart home:
You press a button (event).
The system runs a handler that turns on the lights.
As a tester, you’d check:
Did the lights actually turn on?
What happens if the button is pressed twice?
What if the handler fails?
Event-driven systems: A handler reacts when something happens (e.g., a user signs up)
Understanding handlers helps you:
Know where the logic lives — so you can test the right thing.
Understand how data flows throughout the system.
Spot side effects — like database updates or messages sent.
Write better unit or integration tests by targeting the handler’s behaviour.
Most conferences end when you walk out the door. hashtag#MoTaCon doesn’t.
It lingers.
- In the conversations that turn into ideas.
- In the ideas that turn into experiments.
- In the people w...
The expression says it all when we saw Mark's creative visiting card.
Selfie time with awesome people
02/10/25.
It's Thursday. The time is 16:03. It's Day 2 of MoTaCon. And I've never seen the 99-Second Talks queue grow so quickly. And even after this photo more people turned up.
Such is the...
Glad to be in this learning opportunity around Contract Testing with Marie Cruz and Lewis Prescott.
Glad to finally be immersed into some of the brilliant minds in the Testing space here at MoTaCon
About Me:
I’m coming from: Coventry, UK
My role is: Sr.Test Engineer
I’d love to meet others who are into: exploratory testing, team building, shaping team culture.
I'm coming to TestBas...
A collection of resources to help individuals dive into Public Speaking