Test run considerations for Selenium tests
Before you can run Selenium tests on HCL OneTest™ Server, you must read the considerations that you must take into account and complete the tasks indicated.
Before you run Selenium tests, you must have completed the following tasks:
- You must ensure that the JUnit extension on HCL OneTest™ Server is enabled. You must enable the JUnit extension at the time of installation of the server software or before you add the repository that contains the Selenium tests to the server project. See Enabling server extensions.
- You must have created the Selenium tests that use JDK 8, as part of a Maven
V3.6.3 project. The Maven project must contain the Maven Surefire plug-in, which
is required to run the Selenium tests contained in the Maven project. The Maven
project as a pom.xml must be committed to a remote Git
repository.Note: If you create the Selenium tests on other versions of JDK, you must copy the JDK version to the userlibs pod under the /data/junit-ext/jdks directory. See Copying third-party application Jars to Kubernetes.
- You must ensure that the following flags are configured in the Selenium test:
- Firefox is configured as the web browser to run the test.
- Firefox is enabled to accept all certificates (secured and unsecured).
- Firefox is configured to not display alerting messages when the test runs in the Firefox browser.
- You must set the system property to point to the Firefox driver
(linux_x64_geckodriver) that is provided along with the
JUnit server extension and is available in the /tmp folder.
For example,
System.setProperty("webdriver.gecko.driver", "/tmp/linux_x64_geckodriver")
Restriction: You cannot run the test assets
on a remote Docker host.