It has been a few years since I have tried it, but QARun used to work well with Oracle. Oracle testing required the use of a piece of code to "expose" the fields to QARun. The QARun documentation will tell you how to configure the application (Oracle Forms) to work.
If you do not use the plugin, the forms will only present one field to the user. Your Script will appear to only interact with that one field. You are reduced to scripting the page as if it were a character based application.
Seretta, the code that Cupal is talking about is Rendering. You need to ask your developers of the forms to turn Rendering "ON". By default it is normally turned off and this causes QARun to see the entire screen as 1 big bitmap. With Rendering "ON" it allows QARun to see different fields within the Screen.
Cupal, if you get this send me an email at: SBoone@BBandT.com haven't talked to you in a few years [img]images/icons/smile.gif[/img]
We have stable, maintainable scripts for OracleForms 6i. The last couple releases have addressed most issues.
The hardest part is creating unique but reusable object maps for popups and such (works best if I actually turn off Attach Using 4GL, create the object map, then turn it back on). Also syncronization as QARun can't seem to tell when the forms are busy - we created a function to check the state of the mouse pointer (hourglass). And capturing displayed data (like text in an edit or grid) can get tricky.
All in all, it is working well. I don't have any experience with other automation tools on Oracle Forms, so I don't know how QARun matches up. But with the function library we have now after 2 years, we can automate new functionality easily and have yet to not be able to automate something (with the latest release of QARun).
A problem is a difference between what is perceived and what is desired, that
we want to reduce (Dewey 1933)