Work
Examples of how I look at product quality in practice.
Professional QA experience and independent product observations. Context is anonymised where required.
01 · From my QA experience
The expected checkout path passed. An alternative route reached order confirmation at €0.
The rule
If the pricing service failed and returned €0, checkout had to be blocked. The standard journey enforced that rule correctly.
What I tested
During exploratory testing, I changed one element in the page URL and followed an alternative route through the flow.
What I found
The block disappeared. The flow reached order confirmation with a price of €0, even though the business rule should have prevented that state.
Why it matters
The rule worked on the expected path and could be bypassed through another path. Testing the intent of the rule exposed a scenario the standard journey did not.
What this shows
Business-rule thinking
The test followed the intent of the pricing rule, not only the steps in the standard checkout journey.
Alternative paths
A small change in how the flow was entered exposed behaviour the expected route did not.
Risk visibility
The issue could result in an order being confirmed at €0, turning a technical gap into a direct commercial risk.
About this example. It comes from my professional QA experience and is anonymised to protect product and company context.
02 · Independent product observation
Correct ranking information could still be interpreted in two different ways.
The context
An education platform displayed a ranking status as “Top 2”.
The first time I asked what it meant, the explanation was that the user was in first place, with another user on the same score.
Later, the same “Top 2” status appeared in a situation where there was a higher score above it.
What I looked at
I compared the two situations and the explanations behind them to understand whether the information displayed gave the user enough context to interpret the ranking correctly.
What I found
The calculation and the information displayed were correct in both situations.
The same wording could still be interpreted differently depending on the context:
- first place with an equal score
- second place behind a higher score
The interface did not provide enough context to tell which situation applied.
Why it matters
Correct information can still be difficult to interpret when the interface does not provide enough context around it.
In this case, the user needed additional information outside the product to understand the exact position.
Outcome
The ranking display was later updated from the broader “Top 2” wording to an explicit position, such as “2nd place”, making the information clearer for users.
About this example. Independent product observation, anonymised and published with the organisation’s approval.
Have a workflow that deserves a closer look?
Tell me what the product does, where quality sits in the team and what prompted you to look for support.
Start a conversation