Blog   Madness BUGs Classification

Madness BUGs Classification

By Author
0

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.
zombi_del_dibujo_animado_pegatina_redonda-r56cd8a07a46b475b90c7e3378cbc40c2_v9waf_8byvr_324Rocky – 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

Related Posts

Thankful Hearts, Helpful Hands: QA for E-Commerce Business

By Anna Senchenko
1+
You`ll definitely be cooking and eating up a storm today, and it can be easy to forget the core meaning of Thanksgiving. It`s high time to reflect on what makes you thankful! The
Read more

Bug or Treat! What are software testers biggest fears?

By Anna Senchenko
1+
Halloween 🎃 is here and it’s time to think of the most terrifying things in work of QA specialists. Our testing team unites young, brave, highly motivated experts, who strive to find even
Read more

What Is Regression Testing And How To Run It?

By Anna Senchenko
1+
Regression testing is the type of testing that helps to make sure that code changes don’t impact on existing program features. It has to be performed for the validation of data modification. A
Read more

The Artificial Intelligence Impact On Software Testing

By Anna Senchenko
1+
A software testing, performed by human resources, still has its value, but due to artificial intelligence, the process became more productive, quicker, and easier. Some specialists are sure that in the near future
Read more

Get Ready For Pre-Holiday Madness: Load Testing Is A Key For Survival

By Anna Senchenko
1+
Load testing can be perceived as a kind of performance checking. Mentioned type of testing shows the efficiency of a system productivity under real-life load conditions. Such checking helps to understand the behavior of
Read more

Blog