3 ms·
> dev, test, and e2e tests should be done against full-size db clones that's cute, what is your "full-size"? I don't have 2 days to run a test, and I'm pretty
by axlee 4y ago
> dev, test, and e2e tests should be done against full-size db clones
that's cute, what is your "full-size"? I don't have 2 days to run a test, and I'm pretty sure every single compliance requirements we are following would get obliterated the second someone hears about us doing that
- samokhvalov 4y agoAgreed on compliance part – of course, in many cases (not in all though) PII must not be in dev/test envs. Although, cannot agree with the former part. If your tests are running 2 days on a full size clone, and it's an OLTP case, what about users, do they suffer from long query duration too? It sounds like it's time to optimize queries and/or redesign test sets (or both). If it's bad in testing, it will be bad in prod. That's the idea of testing. Example: how do you check schema changes?
- eddsh1994 4y agoYou have a tool to keep the structure of data but anonymize it, I’ve seen this a few times in healthcare regulated systems
- Foobar8568 4y agoI am laughing each time I hear this so call anonymous process /data. Each time, there were different ways to link back data or things were badly scraped.