MSAMM
Back to course

Oracle Visual Builder: Applications That Outlive Their First Release · Module 17 · Quarterly updates and VBCS

Testing in the update window

Lesson 168 of 176 · 3 min

The ORDER ACROSS ENVIRONMENTS, HOW MUCH TIME YOU GET, and WHAT TO DO WHEN A DEFECT APPEARS WITH TWO DAYS LEFT. The window exists because non-production environments are patched before production, and it is the only period in which you can see the future and still change something. THE ORDER IS THE OPPORTUNITY: TEST FIRST, PRODUCTION LATER. So the whole plan is to run Lesson 4's pack against the patched test environment while production is still on the current release. HOW MUCH TIME YOU GET IS FIXED, PUBLISHED, AND USUALLY SHORTER THAN PEOPLE ASSUME. Which is why the pack has to be an hour rather than a day — the window is not the constraint on quality, the pack's size is. AND THE FIRST DAY IS WORTH MORE THAN THE LAST, WHICH IS THE PART TO ACT ON. A defect found on day one has the whole window for a

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Oracle Visual Builder: Applications That Outlive Their First Release, 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 17 · Quarterly updates and VBCS

  1. 1Two calendars, not one
  2. 2Reading a release note for risk
  3. 3Component and runtime versions
  4. 4A regression pack for an application
  5. 5Testing in the update window
  6. 6What breaks: after the update
  7. 7Lab briefing · Assess a real release note