MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 16 · Environments: what test must not have

How many environments, and why

Lesson 162 of 184 · 3 min

Development, test, training and production is the common shape. WHAT EACH EARNS ITS COST BY DOING. Every environment costs storage, licences, administration and a share of every patch cycle — so each one has to justify itself, and an estate with seven environments usually has three that nobody could explain. DEVELOPMENT IS WHERE THINGS ARE BUILT AND BROKEN, AND ITS DEFINING PROPERTY IS THAT NOBODY MINDS. It can be unstable, it can be refreshed at short notice, and it does not need production's data volume. An estate whose developers work on a system anybody else depends on has no development environment, whatever it is called. TEST IS WHERE THINGS ARE PROVEN, AND ITS DEFINING PROPERTY IS THAT IT MATCHES PRODUCTION. Same patch level, same configuration, realistic volume — Lesson 5 — because a test on an environment that differs tests a different system. That match is the entire reason it

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Oracle Apps DBA: Keeping E-Business Suite Alive, with a certificate on completion and a fourteen-day refund window.

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

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