1 upvotes, 0 direct replies (showing 0)
View submission: Massive Failure on the Product
It depends how you run it I guess and what your security and access permission management is like, but generally
Dev/ local env - just the workstation plus a local DB for testing at the dev's convenience
Test/QA - a server made for handling test data and integration with client - frontend , testers and devs both use this when needing to test network apis against their app
Integration /Staging - a pre-prod environment that should simulate the exact same server setup and data as prod, this is where you may have differences depending on your company policies. If you can't access real data out of security concerns, you should atleast simulate near identical traffic and data sizes and variety. Extensive testing is necessary at this stage, arguably the most important yet often looked over env. Dev ops, DBAs and QA should be most involved with this stage, as devs should have verified their code by test env and their CI/CD.
Production - but the time you are here big bugs should've been resolved by Test and QA and staging should've resolved high traffic scenarios and different prod like configurations.
In the scenario op described, there should have been a large data reference for the staging env to work and test against that simulated the exact time lines and data sets of the prod env. Hindsight is 20/20 but I feel like dealing with existing records is a pretty basic situation and this is a massive lack of oversight in that regard.
There's nothing here!