MSAMM
Back to course

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

Testing both locales

Lesson 160 of 176 · 3 min

EVERY SCREEN TWICE, because a right-to-left layout is A DIFFERENT LAYOUT and A DEFECT THERE IS INVISIBLE IN THE OTHER LANGUAGE. This is the check most often skipped and the one with the largest affected population in this estate, and the reason it is skipped is that the developer does not read the other locale. THE FIRST THING TO INTERNALISE IS THAT IT IS NOT A TRANSLATION CHECK. The words being right is the easy half. The layout mirrors, so element order reverses, alignment flips, and anything with a hardcoded direction lands in the wrong place — Module 7 Lesson 5. SO EVERY SCREEN IS TWO SCREENS AND A DEFECT IN ONE IS GENUINELY ABSENT FROM THE OTHER. Which is why "I tested it" means half of it unless somebody says otherwise. THE NUMERAL TRAP IS THE SPECIFIC THING TO LOOK FOR AND IT IS EASY TO SEE ONCE YOU

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