What test must not have

Real salaries, real bank details, working email, live integrations and A ROUTE TO THE OUTSIDE WORLD. EVERY ONE OF THOSE HAS CAUSED A REAL INCIDENT. Module 6 Lesson 5 lists what a clone carries; this is the same list stated as a prohibition, because the clone is where a test environment gets all of it. WORKING EMAIL IS FIRST BECAUSE IT REACHES CUSTOMERS AND CANNOT BE RECALLED. A test batch sends real invoices to real addresses — and the damage is not technical, it is a client's customers receiving something untrue and their support desk taking the calls. Disable it at the system level rather than trusting a setting somebody can change. LIVE INTEGRATIONS ARE SECOND AND WORSE IN ONE RESPECT: THEY WRITE. A database link that still resolves to production, an interface directory shared with a bank, a service another system calls. A test on that environment can corrupt…

In this module: Module 16 · Environments: what test must not have

1. 1How many environments, and why
2. 2What test must not haveFree preview
3. 3Masking, and its limits
4. 4Refresh cadence, and who decides
5. 5Keeping environments comparable
6. 6Access, per environment
7. 7Documenting an estate
8. 8What breaks: three environment failures
9. 9Lab briefing · Write the handover pack