
You are building and maintaining an automated test suite for a product that runs across staging, UAT, and production-like environments. The suite covers user signup, subscription changes, content access, and API-driven workflows, so test data can easily drift, become stale, or create false failures if it is not managed carefully.
How do you manage test data across different environments in an automated suite, and how would your approach change for staging, UAT, and production?