Madness BUGs Classification

Reading Time: 3 minutes

Do you want to see the reverse side of the testers world?
As you may know, we love to organize things (You betcha!). To Do Lists, schedules, graphics, classification, reports, boxes of things etc. Do you think it’s boring?
No way! Especially in the IT world!
This desire made QA Madness team create fun and useful slang that we use with our co-workers. The other day, our testers created nicknames for each bug that they found during their work and use this classification daily. How’s that happened and what they’ve made? See yourself:
The story started on the moment when one of the developers couldn’t reproduce the issue reported by me. After investigations appeared that issue was reproduced only with my one test account and nowhere else. The developer called this issue “Unicorn” and I really liked this name. I shared it with my colleagues and we decided to create our own Mad bug classification:
Dementor – critical or hard to find bug marked as ‘Won’t fix”.
Pixy – the trivial bug that is reproduced from time to time.
Unicorn – a weird bug reproduced only for one user.
Poltergeist – a bug with random reproducibility.
Vampire – a bug that sucks the DEV’s and QA’s nerves while dealing with it.
Phoenix – the bug that starts to reproduce right after it has been fixed and resolved.
Nearly Headless Nick – nearly completely fixed bug.
Doppelganger – the same bug reported by several QAs at once.
Avada Kedavra – Fatal error or crash.

Hydra – resolving of this bug will cause several new.
Zombiea bug that stalks you on all projects.

Rocky
– a bug which is reopened and resolved several times in a row.

Loki – a very tricky bug.
Ghost – the bug that reported but no one pays attention to it.
Gorgon – blocker bug.
Shapeshifter – the bug steps to reproduce of which change before the developer starts fixing it.
Werewolf – a bug which turns out to be a feature.
Boggart – the bug that you found but haven’t reported yet, so it still exists in the system and keeps causing weird phenomena.
Barghest – a bug that appears on the day of the release.
 
So when somebody asks you about Unicorn, you will know that this person deadly serious and not schizophrenic. Maybe it’s just our tester! 😉
 
Post created by:
Natasha Gubenko
Roman Barabash
Nina Panevina
Kostya Koberidze
Natalia Vedmid

Author

Recent Posts

What an External QA Audit Actually Does (And Why the Real Picture Matters More Than a Clean One)

Last reviewed: June 2026 When an external audit is scheduled, most engineering teams do what…

3 weeks ago

Smarter Testing Starts Here: A Complete Guide to Integrating AI-Powered QA into Your Existing Workflow

Last updated: May 29, 2026 The average developer now ships 7,839 lines of code per…

1 month ago

10 Best QA Testing Companies in 2026 (Ranked and Reviewed)

Last updated: May 28, 2026 Choosing the wrong QA partner isn’t just a minor misstep…

1 month ago

The Executive’s Guide to Web Testing Automation 2026

In 2026, your website is your storefront, your sales rep, and your reputation – all…

2 months ago

Building a Reliable Automation Testing Process in 2026

If you are running a digital business in 2026, you’ve likely heard that automation is…

3 months ago

What Is Security Testing Automation of 2026 and How to Get There

With the sharp shift in how cyber resilience is approached and the EU’s CRA introducing…

3 months ago