I worked in games QA for 6 years becoming a lead for huge teams on AAA projects.  Most of my teams where made up on inexperienced testers as we'd bulk hire temp workers for large titles.  But claiming because these testers where just sending minor issues caused the issue is bollocks, the Producers and QA leads and management should be working together to prioritize bugs based on severity and work on them first, most graphical, collision and audio issues iron themselves out as development moves forward and a full retest of lesser issues is usually done to clear out the bug database later down the line.<br><br>Sounds like CD Project Red is trying to point the finger again,(reply>), I suspect they also had more than one QA studio with 30 people, for the size of the project that it is.<br><br>And yeah they knew. Everyone knew. Like you wouldn't know every single bug but you do get a feel for the state of the project as you're working with it.,(reply>), @Neo Saturos Agreed, its honestly neither the Devs or QA but Management that is at fault.,(reply>), @Nobal Kain The devs probably would indeed have fixed or at least seen many of the issues present, if it wasn't for the management and shareholders enforcing a December 2020 release - about a year before the game was ready, as the devs apparently felt. Quantic Lab and CD Projekt are both to blame, their leaderships especially.,(reply>), As a former QA Tester over 10 years ago I also call BS on this. There is no way CDPR did not know the state the Game was in at the time of launch. People seem to think Devs stare at Code all day and dont actually play the Game. They play it every day and all they had to do was turn it on and they would have seen these issues. This sounds like a QA Tester that only did this one Game and pictured something different in his head. QA has no power, they report and the Devs fix or they dont.