Environment setup and customization

Setup

The setup for the UI automation tests is similar to the setup for the regular metadata unit tests and uses the same infrastructure.

You will need to include the latest Selenium WebDriver in your in third-party folder.

For developers, this setting already defaults to the directory specified by the eclipse classpath variable THIRD_PARTY.
Otherwise, specify a root folder which contains all folders prefixed with selenium-webdriver-* from \sv-build-file\3^rd Party\packages.

Create or find the appropriate .utest file in your finance or relevant project.
Launch the AFL portal.
Use the automation recorder (Ctrl + F11) to perform the use case you want to automate.
Export the recorded script.
Add assertions.
Run the tests in the unit test player, and make fixes if they fail.
Once the tests pass, have your code reviewed.

The following table represents the properties NexJ uses to customize the UI test runs in NexJ Finance Portal.

Property	Description	Default Value
`uitest.defaultBrowser`	The browser type.	CH
`uitest.browsers`	The list of valid browser types, defined in the properties file.	IE, CH, FF
`uitest.maximumWait`	The timeout for a Selenium wait in milliseconds.	15000
`uitest.screenshotsEnabled`	Take a screenshot when the test is completed.	Defaults to true if `uitest.screenshotDir` is specified, or false otherwise
`uitest.headless`	Runs the test in headless mode.	true
`uitest.screenshotDir`	Root folder that screenshots should be stored into.	null
`uitest.webdriverDir`	Path to the executable web driver file.	A setting controlled by NexJ Studio preferences. This is the only required setting to run UI automation.
`uitest.locale`	Sets browser locale. The following runs the test(s) in French: `-Dnexj.uitest.locale="fr"`	Default system language

To change any of these property values from NexJ Studio Tool Settings:

Select Window > Preferences > NexJ Studio > Launch Settings > Tool Settings > Run Unit Tests.
In the VM arguments field, enter:
-Dnexj.[property] = value