Blog   Madness BUGs Classification

Madness BUGs Classification

By Author
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-imageDementor – 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.
Cortesia_the_UnicornNearly 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.

– 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.
tumblr_static_big_deuce_skullWerewolf – 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

Latest Posts

Software Testing Outsource – FAQs Revealed

By Yana Andyol
Reading Time: 5 minutes Since the outsource of software testing services is a multi-faceted process, it is natural for the questions to occur at any stage of cooperation with a software testing company. This is the reason
Read more

Misconceptions of the Automated Testing Debunked

By Yana Andyol
Reading Time: 4 minutes Recently, automated software testing has been widely identified as game-changer for software projects. With artificial intelligence quickly gaining traction, total automation sounds like an inevitable reality. Yet those jumping to conclusions gave birth
Read more

Cutting-Edge Technology: The Era of Disruptive Innovation

By Yana Andyol
Reading Time: 5 minutes Today are the times when an idea is turned into a real business so easily and so quickly. Start-up and middle-sized businesses are rising up and challenge the status-quo of the incumbent companies
Read more

Testing Time Estimation Methods: Factors to Encounter

By Yana Andyol
Reading Time: 4 minutes Often, management of the companies that outsource QA services asks to analyze the time required for testing efforts. But this index is hard to predict, a range of aspects elude the measurement. Some
Read more

Small Business Migration Alternative: Shopware vs. Magento 2

By Yana Andyol
Reading Time: 4 minutes The dynamic world of eCommerce is full of the events shaping the industry today and the future direction of its growth. Adobe acquisition of Magento triggered several subjects for debate. One of the
Read more