local-grid-parent

In this release, I reverted to version 1.4.4 of PhantomJSDriver, which is the latest release that's compatible with Selenium 3. I also upgraded to the latest release of Selenium Foundation (version 27.0.8), which isn't strictly necessary but keeps everything in sync.

In this release, I upgraded to the latest release of Selenium Foundation (version 27.0.6). I upgraded several other dependencies as well:

• JUnit Fountation: 17.0.2 → 17.0.3
• HtmlUnit: 2.67.0 → 2.70.0
• PhantomJSDriver: 1.4.4 → 1.5.0
• Commons Text: 1.9 → 1.10.0
• OKHTTP: 4.9.1 → 4.10.0
• Kotlin: 1.5.20 → 1.8.10

I also added information in README regarding execution of the local-grid-parent unit tests, as this can prove vexing if not configured properly.

This is primarily a maintenance release to stay in sync with the latest release of Selenium Foundation. This foundation release was primarily focused on adding browser profiles to the Gradle project file and included only minor tweaks to core local Grid functionality.

In this release, I upgraded Selenium Foundation from v26.6.0 to v26.7.0. This release resolved an inconsistency in the specification of browser plugins which could lead to puzzling failures. I also applied refined patterns to the unit test configuration of this project that I developed in Selenium Foundation.

In this release, I added the ability to attach local node servers to an active Grid collection. These can either extend the set of "personalities" supported by the Grid or provide additional sessions of "personalities" that are already supported.

In this release, I upgraded HtmlUnitDriver to the latest release (version 2.64.0)

In this release, I upgraded to the latest Selenium Foundation release (version 26.5.0), which features improved local Grid launch behavior.

To eliminate the need to specify the appium.with.pm2 property to command line or settings file, I've now added this property to the Appium-related profiles in the local-grid-hub project definition (POM) file.

There was a bug in Selenium Foundation that resulted in a NullPointerException failure affecting the shutdown feature of this project. Upgrading to the latest release resolves this issue.

In this release, I add three Grid node profiles to the local-grid-hub project that I had failed to include in the pull requests that added these node types to the parent project. I also updated the README to document these new profiles.

In this release, I added a new node module that uses the Appium XCUITest engine to enable automated interactions with iOS applications.

In this release, I added a new node module that uses the Appium Mac2 engine to enable automated interactions with Macintosh applications. This turned into much more of a learning experience than I expected given the relative ease with which I was able to add support for this engine in the core Selenium Foundation library. Turns out that the path inherited by Java processed spawned by CommandLine isn't always what might be hoped. This wasn't apparent in the foundation unit tests, which inherit the System path and class loader from the test runner. When launching stand-alone Selenium Grid servers, however, the omissions in the provided System path and class path proved fatal.

I discovered that I failed to propagate the Appium settings to the Grid server processes, and that my use of the "working directory" in the Appium node plugins was flawed. Four patches later, I think I finally stomped out the last of the bugs in this swarm.

I added the Apache 2 license, which I'd neglected to do previously, and I did a bit of tidying up as well - adding final modifiers to class fields where possible and fixing swapped expected/actual arguments in unit test assertions.

In this release, I upgraded to the latest release of Selenium Foundation (26.2.0). This new release enables support for automating interactions with Windows native applications via the Appium WinAppDriver engine.

This release is just housekeeping... I migrated the driver version specifications from the individual node modules to the dependency management block in the parent POM. This centralizes these specifications and makes maintenance a bit easier.

This should have been included in the last local-grid-parent release, but I rushed the process and missed this module dependency.

Just to stay current, I updated to the latest release of Selenium Foundation (26.1.2-s3). This update merely bumped the HtmlUnitDriver dependency.

In this release, I updated to the latest Selenium Foundation and JUnit Foundation libraries.

In this release, I upgraded to the latest release of Selenium Foundation (26.1.0). This new release enables support for automating interactions with Android native applications via the Appium Espresso engine.

In this release, I fixed all of the tests that I broke in the last release by adding a dependency context that was only available in the local-grid-hub project. To correct this, all I needed to do was to upgrade to the latest release of JUnit Foundation (17.0.0). I also got bitten by the relocation of the Appium unit test API demos application. Timing is often important.

In this release, I implemented a new UiAutomator2 grid node that enables automated testing on Android applications via Appium. This required tweaking the implementation of Selenium Foundation to enable management of stand-alone Appium node servers. To get the unit test to work as expected, I also needed to propagate the local-uiautomator2-node resource folder path to the local-grid-hub process, to provide a couple of necessary settings. (This is probably too complicated, and it's definitely fragile.)