The Scariest Words in Game QA: Halloween Glossary

A Heisenbug is a defect that changes or disappears the moment you try to observe it. Attach a debugger, add logging, or slow the build down, and suddenly everything works perfectly.

It is the poltergeist of game development. You know it is there because you saw the crash with your own eyes. But the second you call someone over to look, the house goes quiet.

You wrote the perfect bug report. Clear steps, screenshots, a video, the exact build number. Then it comes back marked “CNR” and closed.

Somewhere out there, a player will hit that exact bug on launch day. Until then, it waits in the dark, patiently. Good testers log frequency rates and environment details precisely so this ghost has fewer places to hide.

The game hasn’t crashed. The music is still playing. Your character can still move. But the door won’t open, the NPC won’t talk, and there is no way forward.

A soft lock is the haunted-house room with no exit. It is especially terrifying when it strikes after an autosave, sealing the player in for good.

Everything runs beautifully for the first hour. Then the frame rate dips. Load times stretch. Four hours in, the whole thing collapses.

A memory leak happens when the game keeps claiming memory and never gives it back. It is a curse that drains the life from your hardware a little at a time, which is why soak testing (leaving builds running for hours or days) is every QA team’s garlic and holy water.

You fixed it. It was verified. It was closed. You even celebrated.

Then a new build drops, and the bug you buried three sprints ago claws its way back out of the ground. Regressions are the undead of QA, and the only reliable stake through the heart is a solid regression test suite run on every build.

One hundred hours of progress. Every side quest, every rare item, every carefully named horse. Gone.

Few bugs inspire genuine player rage like a corrupted save file. It is the jump scare nobody laughs about afterwards, and it is why testers deliberately pull power cables, fill storage to the brim and quit mid-save, so players never have to find out the hard way.

One wrong jump against the wrong wall, and your character slips through the floor into an endless, empty abyss. The skybox stretches out forever. Nobody can hear you respawn.

Collision bugs and out-of-bounds exploits are the stuff of speedrunner legend, but in testing they are pure dread. QA teams spend hours hugging walls, jumping into corners and squeezing into gaps, so players don’t end up lost in the void.

Before a game can launch on console, it has to pass the platform holder’s certification requirements. Miss one (a wrong button prompt, a mishandled controller disconnect, a missing error message) and the build is sent back.

A cert failure can push a release date, cost a fortune and send the whole team back into crunch. It is the final boss of game QA, and the best way to beat it is with compliance testing done long before submission day.