


Unfortunately, the way that AppiumDriverLocalService runs Appium, it does not re-use your defauly PATH and instead reverts to the system default. If you followed the installation instructions for XCUITest driver, Carthage is installed using Homebrew and it is automatically added to the PATH, so this isn't normally an issue. Store the paths in environment variables named NODE_PATH and APPIUM_PATH, and the AppiumServiceBuilder will pick them up automatically.Īnother issue I ran into is that the XCUITest driver requires the Carthage package manager to be in the system PATH. If you share your test code with a team and/or run in different CI environments, you can set this information via environment variables rather than hardcoding file paths in your test code. ServiceBuilder.withAppiumJS(new File("/path/to/appium"))

ingDriverExecutable(new File("/path/to/node/executable")) AppiumServiceBuilder serviceBuilder = new AppiumServiceBuilder()
