Oracle Visual Builder: Applications That Outlive Their First Release · Module 13 · Extending Fusion applications
Testing an extension
Lesson 132 of 176 · 3 min
Against A MOVING TARGET, on an environment that is PATCHED TO A SCHEDULE YOU DO NOT CONTROL. Testing an extension is not testing an application, because half of what you are testing belongs to somebody else and changes without you. WHAT YOU CAN TEST NORMALLY IS YOUR OWN LOGIC. The service calls, the validation, the behaviour of what you built — all of it is yours and none of it is the risk. WHAT YOU CANNOT TEST ONCE IS THE INTEGRATION WITH THE PAGE. That the region appears where it should, that the field it reads is present, that the events it listens for still fire — every one of those depends on a page Oracle owns, and every one is re-tested by the next update whether or not you re-test it. SO THE TESTING QUESTION IS NOT "DOES IT WORK" BUT "WHAT WOULD I CHECK IF THE PAGE MOVED".…
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 13 · Extending Fusion applications
- 1Extending against building beside
- 2What an extension can change
- 3The workspace and the lifecycle
- 4Where this meets Page Composer
- 5Sandboxes and coordination
- 6Testing an extension
- 7Surviving a quarterly update
- 8When to stop extending
- 9What breaks: three extension failures
- 10Lab briefing · Extend, then update