No, this is not a joke.
A British student booked a Ryanair ticket using his Facebook alias:
👉 Adam West
Everything was fine… until reality kicked in.
- Fix the name on the ticket? £220
- Change his legal name + passport? £103
So he made a decision that sounds completely absurd… and yet oddly logical:
👉 He legally became Adam West
👉 He boarded the flight
👉 The system accepted it without any issue
✅ Problem solved. System passed.
And honestly?
If you’ve worked in testing or software long enough…
this story feels a little too familiar.
🧪 When “Making the System Pass” Becomes the Goal
This isn’t just a funny anecdote.
It’s a perfect illustration of something we see in tech every day:
- A system with rigid rules
- A costly or inefficient “official” solution
- A user forced to find a workaround
And suddenly, the goal becomes:
👉 “Make it pass” instead of “make it right.”
🧭 What This Story Teaches Us About Software Testing
✅ 1. Don’t Fix the Symptom — Fix the Root Cause
Adam didn’t fix the ticket.
He fixed the mismatch.
In testing, we often see:
- “Let’s update the test data”
- “Let’s retry until it passes”
Instead of asking:
👉 Why is the system failing in the first place?
Great testers solve problems. They don’t hide them.
✅ 2. The “Official Solution” Isn’t Always the Smart One
£220 for a name correction?
That’s not just expensive — it’s bad design.
Systems often prioritize:
- Rules over usability
- Process over logic
👉 Your role as a tester is to challenge this.
Just because something works… doesn’t mean it makes sense.
✅ 3. Think Like a Tester: Explore Beyond the Obvious
Adam didn’t accept the first option.
He:
- Explored alternatives
- Compared outcomes
- Tested the limits of the system
👉 That’s real exploratory thinking.
Test cases find bugs. Exploration finds truth.
⚠️ 4. Shortcuts Are Smart… Until They Aren’t
This workaround is funny.
But in real systems, shortcuts look like:
- Changing input data to make tests pass
- Relaxing assertions
- Ignoring failing scenarios
👉 This is how silent bugs enter production.
Short-term success. Long-term risk.
🎭 5. Creativity Is Powerful — But Needs Ethics
Creativity is a strength in QA.
It helps you:
- Think outside the box
- Discover edge cases
- Challenge the system
But without ethics?
👉 It becomes manipulation instead of improvement.
Your job is not to trick the system — it’s to improve it.
💰 6. Always Think in Cost vs. Impact
Adam did the math.
| Option | Cost | Outcome |
|---|---|---|
| Fix ticket | £220 | Correct, safe, expected solution |
| Change name | £103 | Clever but extreme workaround with long-term implications |
👉 He optimized for value.
In testing, ask yourself:
- Is this bug critical?
- Is this workaround sustainable?
- What’s the real impact?
Senior QA = smart decision-making.
🚨 7. The Anti-Pattern We All Know
Let’s be honest 😄
You’ve seen this:
- Test fails → change the test
- Assertion fails → relax it
- Bug appears → “works on my machine”
👉 System passes
👉 Quality doesn’t
Funny in this story.
Dangerous in real life.
🎯 Final Takeaway
This story isn’t about travel.
It’s about mindset.
👉 Do you fix problems…
or just make them pass?
Because in the end:
- Anyone can make a system pass
- Anyone can tweak a test
But great testers?
👉 They fix the system — not the illusion.
💬 Over to You
Have you ever seen a “creative workaround” that solved the problem… but didn’t feel quite right?
Emna Ayadi 