MSAMM
Back to course

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

Testing the failure paths

Lesson 159 of 176 · 3 min

A SLOW SERVICE, A FAILED CALL, AN EXPIRED SESSION. Provoking each deliberately, because THESE ARE THE PATHS YOU WILL NEED. The happy path runs whenever things are fine. These three run whenever they are not, which in a real estate is often — and they are the ones nobody has ever seen. SLOW IS THE EASIEST TO PROVOKE AND THE MOST INFORMATIVE. Throttle the network in the browser tools and load the page. What the user sees for four seconds is what you find out — and if it is a finished-looking empty page, that is Module 7 Lesson 8's first defect, invisible at full speed. FAILED IS PROVOKED BY POINTING A CONNECTION AT A BAD URL, AND IT IS THE MOST IMPORTANT OF THE THREE. Module 8 Lesson 7's default is that the chain stops silently — so the check is whether anything appears at all, and whether it

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