Hiram Fleitas rebuilds the QA environment:
In this post I am going to cover how to automatically refresh a lower environment commonly used for testing as part of your release (CD) pipeline.
Well, why? – you may be asking.
- In some cases, developers and testers need to test their application code-changes against a fresh copy of production-like data. This helps them do validations prior to publishing their changes to production where their apps are bombarded by end-user live workloads.
- Also, the lower environment may be used for testing, and we can’t overwrite the test data constantly. It needs to be a hot-standby refresh, made available when necessary.
Click through for notes on the process.