Your QA environment needs 'cattle', not 'pets' (rainforestqa.com)

I've been in the QA space for a while now, and one thing that repeatedly comes up is people neglecting their QA data. It's always an afterthought about how to get their application into the right state to be able to test their functionality properly.

So I'm curious, how do you all manage the seeded test data that you need for your QA tests?

Yes and no. You can't escape at least one "pet" environment, and unless your profit margins are so disgusting that you can rent out dedicated environments for every team, "cattle" tends to be aspirational. If realized, the cattle setup is inevitably abused (spinning up too much, leaving it running and chugging the meter etc...) You're going to have a bad time.