Remove support for Opera and PhantomJS

I finally removed support for Opera, which doesn't provide a W3C-capable driver, and PhantomJS, which hasn't been updated in more than a decade.

Enable web app tests for iOS Safari; optimize platform-specific test skipping

This release is entirely focused on revisions to the unit test suites.

• I added a new IOSSafariGridTest class.
• I enabled the Grid Examples for the XCUITest node sub-project.
• All checks that skip tests based on platform suitability are now performed in @BeforeClass methods to avoid wasting time with a bunch of setup and teardown on tests that won't get run.
• I now only use PM2 for the Mac2 and Windows node sub-projects. Running this configuration more than once per platform is redundant.

Upgrade to latest Selenium dependencies

In this release, I upgraded to the latest Selenium dependencies:

• Selenium libraries: 4.39.0 → 4.40.0
• Selenium Foundation: 30.0.4 → 32.1.4
• HtmlUnit Remote: 4.39.0 → 4.40.1
• HtmlUnit: 4.20.0 → 4.21.0

The changes in Selenium Foundation are quite significant, which warranted incrementing the release minor version.
For details check out the Selenium Foundation release notes.

Ungrade to Selenium-Foundation 30.0.4; update iOS unit test

In this release, I upgraded to the latest release of Selenium Foundation (version 30.0.4). This release resolved issues verifying interactions with iOS sessions by upgrading to the latest Appium iOS test application and using the new Selenium Foundation automation models to interact with it.

I also revised the Windows application unit test to adopt the updated automation model class name.

Upgrade to Selenium Foundation 30.0.3

In this release, I upgraded to the latest release of Selenium Foundation (version 30.0.3). This release revised the handling of Shadow DOM contexts so that special handling only applies to Firefox on Selenium 3. The logic that silently ignores failure in the Shadow DOM unit tests was also refined to only apply to HtmlUnit.

Upgrade to latest Selenium Foundation; improve access to browser-specific unit tests

In this release, I upgraded to the latest release of Selenium Foundation (version 30.0.2). This required updating the unit tests for Mac2, XCUITest, and Windows.

I upgraded several other dependencies as well.

I now use the standard getCurrentCapabilities() method to get the target browser capabilities. I also added settings.properties files for all subprojects. These updates provide much better control over local Grid configuration and target browser for the subproject unit tests.

I also took the time to add JavaDoc everywhere that the compiler complained about.

Upgrade to the latest release of Selenium Foundation

In this release, I upgraded to the latest release of Selenium Foundation (version 29.5.0). This adds enhanced navigation for Android applications.

Upgrade to Selenium Foundation 29.4.1; add Android Chrome tests

In this release, I upgraded to the latest release of Selenium Foundation (version 29.4.1). This release required several dependency updated:

• Selenium: 4.34.0 → 4.36.0
• HtmlUnit Remote: 4.34.0 → 4.36.1
• Appium Client: 9.4.0 → 10.0.0
• HtmlUnit: 4.14.0 → 4.17.0

In addition to these dependency updates, I also added a set of tests for exercising the Chrome browser on Android.

Upgrade HtmlUnit Remote and HtmlUnit to latest releases

In this release, I upgraded HtmlUnit Remote to version 4.34.0 and HtmlUnit to version 4.14.0.

Upgrade foundation; migrate to OSSRH Staging API

In this release, I upgraded to the latest release of Selenium Foundation (version 29.2.2). I also upgraded Selenium (4.34.0), HtmlUnit Remote (4.33.0), and the HtmlUnit headless browser (4.13.0).

To publish this release, I needed to migrate to the new OSSRH Staging API:

• Update publication endpoint URLs
• Upgrade plugins:
  • Maven Release
  • Nexus Staging
  • X-Stream Parser
• There were also a couple of minor issues with the POMs for Local Grid Hub and Local HtmlUnit Node that the old OSSRH system didn't care about, but which the new OSSRH Staging API choked on.

By the way, don't get spooked by the version numbers. Transition to the new release publishing system was a bit bumpy, and I decided not to get persnickety about maintaining the sequence.