device-farm | top level client of aws device farm api

I work on the Device Farm team.

From the output you have shared there could be a few possible reasons.

1. The default test spec file used in Device Farm has a command in the test phase which is:

   "- cd $DEVICEFARM_TEST_PACKAGE_PATH/node_modules/*"

   Since it is not finding the file autoappium.js you want to check if this line was removed from your test spec file.

2. Check installation of node modules in the test spec file under the "install" phase. This looks like:

   echo "Navigate to test package directory

   cd $DEVICEFARM_TEST_PACKAGE_PATH

   npm install *.tgz

   If the modules are not installed then the files would not be picked up.

3. Do you run the test using the same command locally? "node autoappium.js"

   If not, then you should use the same command in place of "- ./node_modules/mocha/bin/mocha test_native_ios.js" as shown in the test spec file comment.

Hope this helps. If this does not resolve, please share the run URL of from the console and I should be able to help you forward with it.

Thanks for posting those logs! It looks like the capabilities are valid(though the bundle id is obviously not valid). The bundleId will automatically be taken from the ipa file so it shouldn't be necessary to provide that if we also have the app capability.

http://appium.io/docs/en/writing-running-appium/caps/#ios-only

Bundle ID of the app under test. Useful for starting an app on a real device or for using other caps which require the bundle ID during test startup. To run a test on a real device using the bundle ID, you may omit the 'app' capability, but you must provide 'udid'.

The default capabilities required for the app to start should be already provided by the default appium server CLI command in the testspec.yml file.

appium --log-timestamp --device-name $DEVICEFARM_DEVICE_NAME --platform-name $DEVICEFARM_DEVICE_PLATFORM_NAME --app $DEVICEFARM_APP_PATH --udid $DEVICEFARM_DEVICE_UDID --automation-name XCUITest --default-capabilities "{\"usePrebuiltWDA\": true, \"derivedDataPath\":\"$DEVICEFARM_WDA_DERIVED_DATA_PATH_V1\"}" >> $DEVICEFARM_LOG_DIR/appiumlog.txt 2>&1 &

Capabilities

Try using classpath:. Note the colon at the end.

There isn’t the output variable in AWS CLI task, you may submit the issue here: https://github.com/aws/aws-vsts-tools/issues

The workaround is that you can get the task logs through Build Log REST API, so you can call REST API to get the task log (e.g. through curl), then extract data from the log.

If you're continuously getting that error I would think something is wrong with the test package. Try running a fuzz test using the same devices and same IPA file. If those execute then it's definitely something wrong with the test package.

Hope that helps.

James.

Also AWS dev support is the greater of $29 or 3% of bill per month. It might just take longer to get a response with that plan than others.

https://aws.amazon.com/premiumsupport/developer-support/