Thanks for posting.
There are, as we understand it, at least two types of Oracle forms.
One type is implemented with the Jinitiator JRE (which is a clone of the
Java JRE), so that the forms processing is done with the application running
like an applet.
The other type is done 100% with JavaScript in the browser.
If you're not seeing this recorded by eValid when you are working with
Oracle Forms the you probably have the first type. In that case, you apply
the same methods that eValid uses for Applets.
* Testing of Java applets within eValid is complicated by the fact
that, to the eValid browser, an applet appears as an opaque
object. eValid has special applet processing and support
commands, described in more detail here:
http://www.e-Valid.com/Products/Documen ... rding.html http://www.e-Valid.com/Products/Documen ... tml#Applet* In addition to its ability to record/play/analyze web-faced applications,
eValid includes a capability to record non-browser applications, and
also desktop objects. Please see:
http://www.e-Valid.com/Products/Documen ... .mode.htmlThe pure-Javacript form of Oracle Forms, which we understand
is the more modern type, tests directly in object mode with eValid
using eValid's build-in DOM sensing and event tracking. You may
need to turn on "element mouseovers" option by toggling Alt+F11
during recording.