Oracle Visual Builder: Applications That Outlive Their First Release · Module 16 · Testing an application with no test framework
Lab briefing · A test plan somebody would sign
Lesson 163 of 176 · 3 min
Write and execute a plan covering DATA, FAILURE, BOTH LOCALES AND KEYBOARD ACCESS — then HAVE IT REVIEWED AS A DELIVERABLE. The last instruction is what makes this a lab. A test plan nobody reads is a document; one somebody reviews is a deliverable with a standard. WRITE IT AS SPECIFIC OBSERVATIONS, NOT AS INTENTIONS. "Open the list with a filter matching nothing; the page says no results match and offers to clear the filter" is a test. "Test the empty state" is a note to yourself, and it cannot be executed by anybody else or checked by anybody at all. COVER THE FOUR AREAS AND KEEP THEM SEPARATE, BECAUSE THEY FIND DIFFERENT THINGS. Data from Lesson 2 — empty, missing fields, long strings, Arabic names, a record with forty lines. Failure from Lesson 4 — slow, failed read, failed write, expired session. Both locales from Lesson 5, and keyboard…
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.
In this module: Module 16 · Testing an application with no test framework
- 1What "tested" means hereFree preview
- 2Choosing data that would fail
- 3Testing without the other system
- 4Testing the failure paths
- 5Testing both locales
- 6Accessibility and keyboard
- 7What breaks: the sign-off that proved nothing
- 8Lab briefing · A test plan somebody would sign