MSAMM
Back to course

Oracle Visual Builder: Applications That Outlive Their First Release · Module 16 · Testing an application with no test framework

Choosing data that would fail

Lesson 157 of 176 · 3 min

EMPTY LISTS, MISSING FIELDS, VERY LONG STRINGS, NON-LATIN NAMES, and A RECORD WITH FORTY LINES. Data chosen to BREAK IT rather than to DEMONSTRATE IT. Your test data is the reason your application works, and it was chosen for convenience without anybody deciding to choose it. AN EMPTY LIST IS THE FIRST AND MOST OFTEN MISSED. Every new customer sees it, and it is the state most likely to render as a blank rectangle indistinguishable from a broken page — Module 7 Lesson 8. It is also the easiest to produce: a filter matching nothing. MISSING FIELDS ARE SECOND, AND REAL RECORDS ARE FULL OF THEM. Your test record has every field populated because you created it; a record from the business has a blank middle name, no second address line, an empty note. A layout with a hole where an empty field sits looks broken — Module 3 Lesson

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 16 · Testing an application with no test framework

  1. 1What "tested" means hereFree preview
  2. 2Choosing data that would fail
  3. 3Testing without the other system
  4. 4Testing the failure paths
  5. 5Testing both locales
  6. 6Accessibility and keyboard
  7. 7What breaks: the sign-off that proved nothing
  8. 8Lab briefing · A test plan somebody would sign
Choosing data that would fail — Oracle Visual Builder: Applications That Outlive Their First Release — MSAMM