MSAMM
Back to course

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

What "tested" means here

Lesson 156 of 176 · 2 min · Free preview

Not "IT WORKED WHEN I CLICKED IT". The FIVE THINGS that must be demonstrated before ANYBODY SIGNS FOR A SCREEN. There is no test framework here, so "tested" means whatever the person saying it decided it means — and this lesson is about making that a specific claim rather than a feeling. THE FIVE ARE: IT WORKS ON DATA CHOSEN TO BREAK IT, IT BEHAVES WHEN THE SERVICE DOES NOT, IT IS CORRECT IN BOTH LOCALES, IT IS OPERABLE WITHOUT A MOUSE, AND THE RULES IT ENFORCES ARE ENFORCED SOMEWHERE THAT MATTERS. NONE OF THOSE IS THE HAPPY PATH, AND THAT IS THE POINT. The happy path is what you demonstrated while building it, several hundred times — it is the least informative check available and it is the one every sign-off consists of. DATA IS FIRST BECAUSE IT IS CHEAPEST AND FINDS THE MOST. Lesson 2, and the developer's

This lesson is free

Watch the full lesson, with its written notes, without an account. It is one of the free lessons this course opens with.

Watch the full lesson

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