@hoboadam_psn said in MLBTS22 : QA is a total failure:
@calikat68_xbl said in MLBTS22 : QA is a total failure:
@luvmyxbox_xbl said in MLBTS22 : QA is a total failure:
Whoever was in charge of QA for MLBTS 22 did a very bad job.
First of all, so many crashes in 22. 21 the game never crashed on me once. 22 is a plethora of crashes in all modes.
Another example : in DD, when I go into choose uniform, the uniform I chose doesn't display on the player - home or away - 21 did not have this problem. You can argue what's the big deal, it's insignificant. I can see that point of view. But the little things add up and show how sloppy this game is.
I can list countless other things but I don't understand how 21 was so tight when it came to QA and how 22 fails miserably in this department. Did they change QA teams for 22? I would be really embarrassed if I was part of that team.
Such a terrible take. QA does catch these issues, however, QA is NOT the team who fixes them. Stop blaming QA and push the issue onto the dev team, who are ultimately responsible.
Sorry, but no matter what a dev team does, QA is the last line of defense here before a patch hits production.
What SDS really needs is a UAT team in production that can test stuff for 24 hours before it hits as a patch. (UAT = User Acceptance Testing)
Devs know how stuff should work. QA should have standard things to look out for, especially for previously "fixed" items. I. Addition, QA should have baseline standards that are tested regardless of what they are testing. Examples include, menu navigation, market transactions, advancing a mini season playoff series, BR rewards etc. UAT should target specific changes. QA should make sure everything works every time.
Now some are going to start saying I don't know what I'm talking about. I've been part of doing DEV, QA, UAT and using stuff in PROD for 15+ years in finance. Nothing goes from DEV to PROD without QA and UAT.
DEV knows how to fix stuff. But you can't just expect an end user to be able to give a Dev the solution. During the QA process, you have steps to check, and you must select pass/fail in the QA reporting environment.
I've merged data and systems for Dean Witter, Discover, Morgan Stanley, Smith Barney, PFPC, DST, First data etc etc etc.
Game companies should have similar QA processes. Most do that I've played. This game, not so much.
Great answer!
Anyone that has ever been part of a decent software development team would agree with you.
I guess the product owner somehow went over the QA team/process due to time/budget constraint.
I know, I know, ambitious ProductOwner rushing things to production against Dev & QA recommendations is something totally new and unheard of in Software development.
Let's hope they'll be able to fix everything as soon as possible!!