Madness BUGs Classification

Madness BUGs Classification

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 - 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.
Zombie - a bug that stalks you on all projects.
Doppelganger - the same bug reported by several QAs at once.
Avada Kedavra - Fatal error or crash.
Rocky - a bug which is reopened and resolved several times in a row.
Loki - a very tricky bug.

Ghost - bug that is 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.
Hydra - resolving of this bug will cause several new.
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

To view or add a comment, sign in

More articles by QA Madness

  • We Don’t Want You to Be Sad!

    Software bugs are not a tornado, tsunami or earthquake, but they can still undermine your company a lot. Obviously…

  • Automated QA Engineer Wanted!

    According to Clutch.co, QA Madness is one of the Top Software Testing Companies in the world that has been successfully…

  • QA Madness B-day

    On the 4th of April, we’ve celebrated the QA Madness birthday! It’s always a pleasure to gather together especially…

  • Virtual Reality. The Testing

    How is the magic created? VR Testing Every performance has a preparation level, or if you want - backstage. That's the…

  • Virtual Reality: One step closer to your dream

    We are bumping into a concept of virtual reality (VR) more and more these days.But I'm pretty sure that not everybody…

  • QA Madness at Top Software Testing Firms 2016

    Clutch.co included QA Madness to the list of Top Software Testing Firms 2016.

  • Announcement: Up-to-date Automated Testing Framework for Magento by QA Madness

    Hello, everyone! We have an announcement for Magento vendors and those who interested in automated testing! The…

  • Magento Moment That Matter

    One day, you’ve decided to launch a new project on your behalf. Online store, lots of items, creative concept.

  • New website announcement

    Today, on April 4th, we're celebrating QA Madness birthday! And to mark this day we’ve prepared a special present for…

  • The Most Common Fears About Automated Testing

    As QA Madness provides an automated testing service along with other different types of manual testing, we decided to…

Others also viewed

Explore content categories