You then move your prod code into the prod-fix or break-fix environment so that it matches current production. Then after all that mess, you do a production change (what you know as a consumer 'patch day'). It's expensive and time consuming to actually thoroughly test anything. Generally when you do things under a heavy load it's just to test 1 specific component (logins, game creates, instance changes, etc.) but not ALL components. You can't generally load test things in any of these environments unless you're specifically set up to do so. Then it goes into STAGE which is a mirror (as closely as possible) to production. Maybe they see if killing cow king prevents creating new cow levels and whether or not the game crashes after a half hour. Then the code is moved to the QA environment where it is basically tested to see if it breaks things in any obvious ways. Let's say your cow king change for example.
Let me explain why.įirst comes DEV, where changes are implemented by developers.
