LabKey uses Selenium to drive our functional UI test automation. The LabKey test team has been migrating our test code to Selenium 3 over the past few months. This will, among other things, allow our tests to run tests against more current releases of Firefox and protect us from incompatibilities with new versions of Java.

We've fixed most of the major issues we've encountered and are close to the home stretch. We have been performing the migration in a separate branch and we will merge our changes back to trunk on Tuesday, December 11.

This update is almost exclusively to test code and the following steps are necessary only if you currently run UI tests locally against trunk with Firefox 45. Selenium tests running under Chrome should continue to work, though there may be new failures due to minor performance variation in the newer version of Selenium. JavaScript test frameworks such as Jest should be unaffected.

After the merge

• Install a current version of Firefox if you don't have it. We've been validating with 62.0.2 on TeamCity. Geckodriver claims to support 57+ but we hit some pretty significant issues with versions as late as 60. We generally recommend using the latest ESR release but there will not be a reliable (for testing) ESR release until next July.
• Make sure server/test/test.properties is up-to-date
  • selenium.firefox.binary should point at a new version of Firefox instead of ESR 45
  • Make sure webtest.webdriver.logging=false. You'll get an unreasonable amount of logging if that isn't set
  • Run a test and make sure it works for you. Nothing in-depth, just make sure it works.

Please bear with us as we iron out the last few kinks over the next couple of weeks. Let us know immediately if you have any concerns or if you have any difficulty after the merge.