MSAMM
Back to course

Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 17 · Release readiness: quarterly updates and regression

Building a regression pack that stays useful

Lesson 166 of 177 · 3 min

A test pack nobody maintains is worse than none, because it is trusted while it is stale — and a green run against tests that no longer exercise anything reads as assurance. KEEP IT SMALL. Fifteen tests that are run every quarter beat two hundred that are run once. The constraint is the update window: whatever cannot be executed in the time between the test environment being updated and production following is not part of the pack, however well written. CHOOSE BY CONSEQUENCE RATHER THAN COVERAGE. Not "which artefacts do we have" but "what would hurt most if it broke on Monday and nobody knew". The month-end reports. The bank interface. The report the CFO reads. The artefact used once a year by two people is not in the pack, and saying so explicitly is what keeps it small. KEEP IT CURRENT by pruning as well as adding. A test…

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.

See the course and enrol9 free lessons

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 17 · Release readiness: quarterly updates and regression

  1. 1Reading an update for riskFree preview
  2. 2What is exposed, and what is safe
  3. 3Building a regression pack that stays useful
  4. 4Testing in the update window
  5. 5New features: opting in deliberately
  6. 6Communicating an update to the business
  7. 7What breaks: after the update landed
  8. 8Lab briefing · Assess a real release note