Oracle Adf Project Configuration For Selenium Testing

Oracle Adf Project Configuration For Selenium Testing

An ADF program is normally optimized for functionality and scalability which means CSS courses and javascript are minified and obfuscated. This makes testing using Selenium extremely tough and brittle.

I have written about those before but a few are even more significant for automatic testing. The ADF Faces documentation also claims lots of configuration changes must be created for automatic testing.

These are the configurations to alter if using automatic testing:
This guarantees that a javascript client element is made for every ADF component regardless of the value of this clientComponent feature on the JSF component. This leaves interacting with the webpage from Selenium much simpler. Additionally, it appears to allow another server and client side attributes. Look for isAutomationEnabled from the ADF source code to get a sense for items that will alter when allowing this. Among those things it enables will be to discover items using range IDs (also referred to as Sub IDs).
In order for this to work you also should place adf-richclient-automation-11.jar on your project classpath. The easiest approach is to simply place this JAR in the WEB-INF/lib folder of your job. The document itself may be located in JDEV_HOME/ /oracle_common/modules/oracle. Possessing readable and deterministic CSS class names which makes it feasible to use CSS selectors on your Selenium scripts. This offers you human readable javascript that makes it a lot easier to determine how to socialize with these scripts out of Selenium. It’s also advisable to receive a copy of this ADF Source code in Oracle Support so that you have the variations with of the inline comments in place. But do not let this frighten you. For easy testing situations you will not be needing javascript interactions. It is only once you need to go all of the way and have quite detailed interactions or evaluations using ADF components.

If you want learn more about Selenium Testing you can join Elegant IT Services.

Javax.faces.PROJECT_STAGE into Development from web.xml as your program will otherwise don’t start since you’ve enabled lots of development-only capabilities. It is possible to revert this to manufacturing using installation plans for different environments.
The above Oracle Software Testing Suite confirmation also advises to place animation-enabled into fictitious in trinidad-config.xml. This isn’t just to hasten the functioning of this testing script because it will not need to await the animations but may also ensure tests do not fail as they would like to socialize with things such as tree nodes prior to the enlarging animation of some tree node is completed. Within my testscripts I also be certain that you execute the javascript AdfPage.PAGE.setAnimationEnabled(untrue)on every page for scenarios where we forgot to put this parameter. Regrettably values in trinidad-config.xml cannot be overridden with installation plans, but there’s a neat hint at which you are able to consult with web.xml context param values from trinidad-config.xml.
You are able to revert these configurations into the optimised values together with installation plans. It’s not necessary to change this from the source code or construct artefact every moment. Simply set the development optimized variants on your source documents so neighborhood runs in JDeveloper utilize the right values. Then use installation programs to reevaluate these for manufacturing and other surroundings.

Leave a Reply

Your email address will not be published. Required fields are marked *


Show Buttons
Hide Buttons