By using AWS re:Post, you agree to the Terms of Use
/AWS Device Farm/

Questions tagged with AWS Device Farm

Sort by most recent
  • 1
  • 90 / page

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Expo build - APK upload fails when using aws-cli command, via GitHub Actions but works from terminal(local)

Command used in GitHub Actions to download APK from expo: latest_build=$(npx eas-cli build:list --status="finished" --distribution="store" --json | jq '[.[] | select(.releaseChannel=="development")][1].artifacts.buildUrl') Command used in GitHub Actions for create-upload and upload in device farm response_upload_app=$(aws devicefarm create-upload --project-arn $DEV_PROJECT_ARN --name latest_build.apk --type ANDROID_APP) curl -T latest_build.apk $url_upload_app Same command when run locally in terminal when the APK is available in a folder, works perfectly fine. Also, at times, when running in local terminal, it was giving request timeout error This is the error log in GitHub Actions in when running get-upload command for the corresponding create upload arn in device farm: "metadata": "{\"errorMessageUrl\":\"https://docs.aws.amazon.com/console/devicefarm/ANDROID_APP_AAPT_DEBUG_BADGING_FAILED\",\"errorMessage\":\"We could not extract information about your Android application package. Please verify that the application package is valid by running the command \\\"aapt debug badging <path to your test package>\\\", and try again after the command does not print any error.\",\"errorCode\":\"ANDROID_APP_AAPT_DEBUG_BADGING_FAILED\"} Debugging done so far: Ran this (aapt debug badging <path to apk>/latest_build.apk ) and was able to get package information correctly
0
answers
0
votes
10
views
asked 9 days ago

error: An unknown server-side error occurred while processing the command. Original error: Cannot start the 'com.XXX.staging' application

Hi all. i got this error while using aws device farm while try to run java appuim testng project: Unable to create a new remote session. Please check the server log for more details. Original error: An unknown server-side error occurred while processing the command. Original error: Cannot start the 'com.XXX.staging' application. Visit https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/android/activity-startup.md for troubleshooting. Original error: 'com.XXX.YYY.ui.activities.MainActivity' or 'com.XXX.staging.com.YYY.core.ui.activities.MainActivity' never started. Visit https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/android/activity-startup.md for troubleshooting Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03' System info: host: 'ip-111-11-11-11', ip: '111.11.11.61', os.name: 'Linux', os.arch: 'amd64', os.version: '3.13.0-139-generic', java.version: '1.8.0_151' Driver info: driver.version: AndroidDriver locally it's run well. i sent this caps for aws server: ------------- AppiumDriver driver; final String URL_STRING = "http://127.0.0.1:4723/wd/hub"; URL url1 = new URL(URL_STRING); --------------- DesiredCapabilities desiredCapabilities = new DesiredCapabilities(); driver = new AndroidDriver(url1, desiredCapabilities); please help, thanks head! Oron.
0
answers
0
votes
16
views
asked 22 days ago

Device Farm Video is not showing application interaction

Hi, I am running my test on device farm. From the test specification log, it shows that my test has passed. However from the video recording, it is always stuck on the default mobile homescreen. How do i get the video recording to capture the test interaction instead of just the homescreen. thanks! ``` [TestNG] INVOKING CONFIGURATION: "Command line test eca2ebbd-c83a-4609-84f0-bb52a16b1afc" - @BeforeTest Tests.LoginTest.setUpPage() [TestNG] PASSED CONFIGURATION: "Command line test eca2ebbd-c83a-4609-84f0-bb52a16b1afc" - @BeforeTest Tests.LoginTest.setUpPage() finished in 118 ms [Invoker 1508395126] Keeping method TestBase.navigateTo()[pri:0, instance:Tests.LoginTest@15975490] for class [TestClass name=class Tests.LoginTest] [Invoker 1508395126] Invoking @BeforeClass TestBase.navigateTo()[pri:0, instance:Tests.LoginTest@15975490] [TestNG] INVOKING CONFIGURATION: "Command line test eca2ebbd-c83a-4609-84f0-bb52a16b1afc" - @BeforeClass Tests.AbstractBaseTests.TestBase.navigateTo() [TestNG] PASSED CONFIGURATION: "Command line test eca2ebbd-c83a-4609-84f0-bb52a16b1afc" - @BeforeClass Tests.AbstractBaseTests.TestBase.navigateTo() finished in 2846 ms [Invoker 1508395126] Keeping method LoginTest.logOut()[pri:0, instance:Tests.LoginTest@15975490] for class [TestClass name=class Tests.LoginTest] [TestNG] INVOKING: "Command line test eca2ebbd-c83a-4609-84f0-bb52a16b1afc" - Tests.LoginTest.loginFail() [Invoker 1508395126] Invoking Tests.LoginTest.loginFail [TestNG] PASSED: "Command line test eca2ebbd-c83a-4609-84f0-bb52a16b1afc" - Tests.LoginTest.loginFail() finished in 7446 ms [Invoker 1508395126] Keeping method LoginTest.logOut()[pri:0, instance:Tests.LoginTest@15975490] for class [TestClass name=class Tests.LoginTest] [Invoker 1508395126] Invoking @AfterMethod LoginTest.logOut()[pri:0, instance:Tests.LoginTest@15975490] [TestNG] INVOKING CONFIGURATION: "Command line test eca2ebbd-c83a-4609-84f0-bb52a16b1afc" - @AfterMethod Tests.LoginTest.logOut() [TestNG] PASSED CONFIGURATION: "Command line test eca2ebbd-c83a-4609-84f0-bb52a16b1afc" - @AfterMethod Tests.LoginTest.logOut() finished in 827 ms [Invoker 1508395126] Keeping method LoginTest.logOut()[pri:0, instance:Tests.LoginTest@15975490] for class [TestClass name=class Tests.LoginTest] ```
0
answers
0
votes
7
views
asked 2 months ago

Webdriver testcases are failing while setting connection

Trying to deploy a basic webdriver.io + nodejs test on devicefarm but always for ios device test cases are getting stuck at Testcase is failing: job arn: arn:aws:devicefarm:us-west-2:612756076442:job:02bd6c95-640d-43b3-82eb-6f618777ac73/1a6364f3-7528-44b1-afa1-d6c2dc51d881/00000 ``` 2022-05-04T22:40:58.353Z ERROR @wdio/runner: Error: Failed to create session. [0-0] Unable to connect to "http://localhost:4723/", make sure browser driver is running on that address. [0-0] If you use services like chromedriver see initialiseServices logs above or in wdio.log file as the service might had problems to start the driver. [0-0] at startWebDriverSession (/private/tmp/scratchY4h2F6.scratch/test-packagex5aknf/node_modules/integration/node_modules/webdriver/build/utils.js:72:15) [0-0] at process.processTicksAndRejections (node:internal/process/task_queues:95:5) [0-0] at async Function.newSession (/private/tmp/scratchY4h2F6.scratch/test-packagex5aknf/node_modules/integration/node_modules/webdriver/build/index.js:46:45) [0-0] at async remote (/private/tmp/scratchY4h2F6.scratch/test-packagex5aknf/node_modules/integration/node_modules/webdriverio/build/index.js:77:22) [0-0] at async Runner._startSession (/private/tmp/scratchY4h2F6.scratch/test-packagex5aknf/node_modules/integration/node_modules/@wdio/runner/build/index.js:223:56) ``` and for android testcases is asking for node version greater than 12 (after adding nvm install 18.1.0 in yaml)
0
answers
0
votes
6
views
asked 2 months ago

Device Farm test setup fails due to 'ascii' codec can't decode byte

I am trying to run Appium Python tests for Android devices. However, my test setup fails with the following error: 'ascii' codec can't decode byte 0xcc in position 58: ordinal not in range(128). My tests run locally just fine, and from the limited information in the logs here I'm unable to decipher where the problem lies. What steps can I take to troubleshoot this issue? Entirety of test setup log is below: ``` [{"attachment_id": null, "parent_id": null, "timestamp": "2022-04-12T23:02:46.018578Z", "level": "Info", "pid": 3106, "data": "Starting Setup Suite", "source": "Harness", "tag": null, "subtype": "Text", "tid": 3111, "type": "Message", "id": 13}, {"attachment_id": null, "parent_id": null, "timestamp": "2022-04-12T23:02:46.019150Z", "level": "Info", "pid": 3106, "data": "Starting Setup Test", "source": "Harness", "tag": null, "subtype": "Text", "tid": 3111, "type": "Message", "id": 15}, {"attachment_id": null, "parent_id": null, "timestamp": "2022-04-12T23:02:48.555726Z", "level": "Debug", "pid": 31496, "data": "Binder ioctl to enable oneway spam detection failed: Invalid argument", "source": "Device", "tag": "ProcessState", "subtype": "Text", "tid": 31496, "type": "Message", "id": 16}, {"attachment_id": null, "parent_id": null, "timestamp": "2022-04-12T23:02:52.875809Z", "level": "Errored", "pid": 3106, "data": "'ascii' codec can't decode byte 0xcc in position 58: ordinal not in range(128)", "source": "Harness", "tag": null, "subtype": "Text", "tid": 3127, "type": "Message", "id": 17}, {"attachment_id": null, "parent_id": null, "timestamp": "2022-04-12T23:02:53.334113Z", "level": "Errored", "pid": 3106, "data": "'ascii' codec can't decode byte 0xcc in position 58: ordinal not in range(128)", "source": "Harness", "tag": null, "subtype": "Text", "tid": 3111, "type": "Message", "id": 22}, {"attachment_id": null, "parent_id": null, "timestamp": "2022-04-12T23:02:53.334757Z", "level": "Info", "pid": 3106, "data": "Finished Setup Test", "source": "Harness", "tag": null, "subtype": "Text", "tid": 3111, "type": "Message", "id": 24}, {"attachment_id": null, "parent_id": null, "timestamp": "2022-04-12T23:02:53.336363Z", "level": "Info", "pid": 3106, "data": "Finished Setup Suite", "source": "Harness", "tag": null, "subtype": "Text", "tid": 3111, "type": "Message", "id": 27}] ```
2
answers
0
votes
7
views
asked 3 months ago

Appium Java Cucumber test scenarios are not executing in the AWS Device Farm

Hi Team, I'm currently trying to execute Appium automated test scenarios on AWS device farm. There are no errors in the log, but no test scenario executed. I have included the testng.xml file which refers to the TestRunner class. ``` [DEVICEFARM] Setting up your device. This usually takes 2-3 minutes. [DEVICEFARM] ########### Start executing testspec ########### [DEVICEFARM] ########### Entering phase install ########### [DeviceFarm] export APPIUM_VERSION=1.14.2 [DeviceFarm] avm $APPIUM_VERSION /usr/bin/avm: line 261: appium: command not found  exists :  [DeviceFarm] ln -s /usr/local/avm/versions/$APPIUM_VERSION/node_modules/.bin/appium /usr/local/avm/versions/$APPIUM_VERSION/node_modules/appium/bin/appium.js [DEVICEFARM] ########### Entering phase pre_test ########### [DeviceFarm] export CLASSPATH=$CLASSPATH:$DEVICEFARM_TESTNG_JAR [DeviceFarm] export CLASSPATH=$CLASSPATH:$DEVICEFARM_TEST_PACKAGE_PATH/* [DeviceFarm] export CLASSPATH=$CLASSPATH:$DEVICEFARM_TEST_PACKAGE_PATH/dependency-jars/* [DeviceFarm] echo "Start appium server" Start appium server [DeviceFarm] appium --log-timestamp --default-capabilities "{\"deviceName\": \"$DEVICEFARM_DEVICE_NAME\", \"platformName\":\"$DEVICEFARM_DEVICE_PLATFORM_NAME\", \"app\":\"$DEVICEFARM_APP_PATH\", \"udid\":\"$DEVICEFARM_DEVICE_UDID\", \"platformVersion\":\"$DEVICEFARM_DEVICE_OS_VERSION\", \"chromedriverExecutable\":\"$DEVICEFARM_CHROMEDRIVER_EXECUTABLE\"}" >> $DEVICEFARM_LOG_DIR/appiumlog.txt 2>&1 & [DeviceFarm] start_appium_timeout=0; while [ true ]; do if [ $start_appium_timeout -gt 60 ]; then echo "appium server never started in 60 seconds. Exiting"; exit 1; fi; grep -i "Appium REST http interface listener started on 0.0.0.0:4723" $DEVICEFARM_LOG_DIR/appiumlog.txt >> /dev/null 2>&1; if [ $? -eq 0 ]; then echo "Appium REST http interface listener started on 0.0.0.0:4723"; break; else echo "Waiting for appium server to start. Sleeping for 1 second"; sleep 1; start_appium_timeout=$((start_appium_timeout+1)); fi; done; Waiting for appium server to start. Sleeping for 1 second Waiting for appium server to start. Sleeping for 1 second Waiting for appium server to start. Sleeping for 1 second Waiting for appium server to start. Sleeping for 1 second Appium REST http interface listener started on 0.0.0.0:4723 [DEVICEFARM] ########### Entering phase test ########### [DeviceFarm] echo "Navigate to test package directory" Navigate to test package directory [DeviceFarm] cd $DEVICEFARM_TEST_PACKAGE_PATH [DeviceFarm] echo "Start Appium JUnit test" Start Appium JUnit test [DeviceFarm] java -Dappium.screenshots.dir=$DEVICEFARM_SCREENSHOT_PATH org.testng.TestNG -junit -testjar *-tests.jar -d $DEVICEFARM_LOG_DIR/test-output [TestNG] Running: /tmp/scratch5Hh0UX.scratch/test-packagezOobaa/testng.xml =============================================== Regression Total tests run: 0, Failures: 0, Skips: 0 =============================================== [DEVICEFARM] ########### Entering phase post_test ########### [DEVICEFARM] ########### Finish executing testspec ########### [DEVICEFARM] ########### Setting upload permissions ########### [DEVICEFARM] Tearing down your device. Your tests report will come shortly. ``` https://us-west-2.console.aws.amazon.com/devicefarm/home?region=us-east-2#/mobile/projects/679dd7ea-c057-48a9-9fa6-cb581cf8133a/runs/716ddf89-b27a-4310-aecf-5eda2f2d7ac2/jobs/00000 Appreciate your help on this issue. Regards, Wathsala.
0
answers
0
votes
5
views
asked 3 months ago

Appium Java tests are not running in the AWS Device Farm

Hello Guys, I am trying to run the appium automated tests with device farm. However, my tests are not running and failing with the below error. ``` [TestNG] RUNNING: Suite: "Command line test 41826786-55ed-4502-bf04-08c38bd76f95" containing "17" Tests (config: null) [Invoker 254801937] Keeping method AndroidBaseTest.setUpAndroidApp(org.testng.ITestContext)[pri:0, instance:mobile.androidapp.androidnativedemo.ApiDemoTestAndroid@32d2fa64] for class [TestClass name=class mobile.androidapp.androidnativedemo.ApiDemoTestAndroid] [Invoker 254801937] Invoking @BeforeClass AndroidBaseTest.setUpAndroidApp(org.testng.ITestContext)[pri:0, instance:mobile.androidapp.androidnativedemo.ApiDemoTestAndroid@32d2fa64] [TestNG] INVOKING CONFIGURATION: "Command line test 41826786-55ed-4502-bf04-08c38bd76f95" - @BeforeClass mobile.androidapp.common.AndroidBaseTest.setUpAndroidApp(org.testng.ITestContext)(value(s): org.testng.TestRunner@71c3b41) Failed to invoke configuration method mobile.androidapp.common.AndroidBaseTest.setUpAndroidApp:The main Appium script does not exist at '/usr/lib/node_modules/appium/build/lib/main.js' [TestNG] FAILED CONFIGURATION: "Command line test 41826786-55ed-4502-bf04-08c38bd76f95" - @BeforeClass mobile.androidapp.common.AndroidBaseTest.setUpAndroidApp(org.testng.ITestContext)(value(s): org.testng.TestRunner@71c3b41) finished in 0 ms [TestNG] io.appium.java_client.service.local.InvalidServerInstanceException: The main Appium script does not exist at '/usr/lib/node_modules/appium/build/lib/main.js' ``` Custom environment yaml file: ``` version: 0.1 phases: install: commands: - export APPIUM_VERSION=1.18.0 - avm $APPIUM_VERSION - ln -s /usr/local/avm/versions/$APPIUM_VERSION/node_modules/.bin/appium /usr/local/avm/versions/$APPIUM_VERSION/node_modules/appium/bin/appium.js pre_test: commands: - export CLASSPATH=$CLASSPATH:$DEVICEFARM_TESTNG_JAR - export CLASSPATH=$CLASSPATH:$DEVICEFARM_TEST_PACKAGE_PATH/* - export CLASSPATH=$CLASSPATH:$DEVICEFARM_TEST_PACKAGE_PATH/dependency-jars/* - echo "Start appium server" - >- appium --log-timestamp --log-level debug:error --default-capabilities "{\"deviceName\": \"$DEVICEFARM_DEVICE_NAME\", \"platformName\":\"$DEVICEFARM_DEVICE_PLATFORM_NAME\", \"app\":\"$DEVICEFARM_APP_PATH\", \"udid\":\"$DEVICEFARM_DEVICE_UDID\", \"platformVersion\":\"$DEVICEFARM_DEVICE_OS_VERSION\", \"chromedriverExecutable\":\"$DEVICEFARM_CHROMEDRIVER_EXECUTABLE\"}" >> $DEVICEFARM_LOG_DIR/appiumlog.txt 2>&1 & - >- start_appium_timeout=0; while [ true ]; do if [ $start_appium_timeout -gt 60 ]; then echo "appium server never started in 60 seconds. Exiting"; exit 1; fi; grep -i "Appium REST http interface listener started on 0.0.0.0:4723" $DEVICEFARM_LOG_DIR/appiumlog.txt >> /dev/null 2>&1; if [ $? -eq 0 ]; then echo "Appium REST http interface listener started on 0.0.0.0:4723"; break; else echo "Waiting for appium server to start. Sleeping for 1 second"; sleep 1; start_appium_timeout=$((start_appium_timeout+1)); fi; done; test: commands: - echo "Navigate to test package directory" - cd $DEVICEFARM_TEST_PACKAGE_PATH - echo "Start Appium TestNG test" - ls -ltr - which appium - echo $JAVA_HOME - which node - node -v - appium -v - java -Dappium.screenshots.dir=$DEVICEFARM_SCREENSHOT_PATH org.testng.TestNG -testjar *-tests.jar -d $DEVICEFARM_LOG_DIR/test-output -verbose 10 post_test: commands: artifacts: # By default, Device Farm will collect your artifacts from following directories - $DEVICEFARM_LOG_DIR ``` https://us-west-2.console.aws.amazon.com/devicefarm/home?region=us-east-1#/mobile/projects/e7d85810-369a-443b-ac29-86ab38065b81/runs/2277ddb7-82ce-4aa5-8d40-3454f1baa009/jobs/00000 Could someone help me ? Regards, Sekar
1
answers
0
votes
45
views
asked 4 months ago

Appium Java Test NG tests are not running in the AWS Device Farm

Hello Guys, I am trying to run the appium Test NG automated tests using teng.xml file with device farm. However, my tests are not running after unzipping the tests.jar file. There is no error in the log file, so I am unable to find out the reason. Custom environment yaml file: ``` version: 0.1 phases: install: commands: # This test execution environment uses Appium version 1.9.1 by default, however we enable you to change it using the Appium version manager (avm). An - export APPIUM_VERSION=1.18.0 - avm $APPIUM_VERSION - ln -s /usr/local/avm/versions/$APPIUM_VERSION/node_modules/.bin/appium /usr/local/avm/versions/$APPIUM_VERSION/node_modules/appium/bin/appium.js # The pre-test phase includes commands that setup your test environment. pre_test: commands: # Setup environment variables for java - export CLASSPATH=$CLASSPATH:$DEVICEFARM_TESTNG_JAR - export CLASSPATH=$CLASSPATH:$DEVICEFARM_TEST_PACKAGE_PATH/* - export CLASSPATH=$CLASSPATH:$DEVICEFARM_TEST_PACKAGE_PATH/dependency-jars/* - echo "Start appium server" - >- appium --log-timestamp --default-capabilities "{\"deviceName\": \"$DEVICEFARM_DEVICE_NAME\", \"platformName\":\"$DEVICEFARM_DEVICE_PLATFORM_NAME\", \"app\":\"$DEVICEFARM_APP_PATH\", \"udid\":\"$DEVICEFARM_DEVICE_UDID\", \"platformVersion\":\"$DEVICEFARM_DEVICE_OS_VERSION\", \"chromedriverExecutable\":\"$DEVICEFARM_CHROMEDRIVER_EXECUTABLE\"}" >> $DEVICEFARM_LOG_DIR/appiumlog.txt 2>&1 & - >- start_appium_timeout=0; while [ true ]; do if [ $start_appium_timeout -gt 60 ]; then echo "appium server never started in 60 seconds. Exiting"; exit 1; fi; grep -i "Appium REST http interface listener started on 0.0.0.0:4723" $DEVICEFARM_LOG_DIR/appiumlog.txt >> /dev/null 2>&1; if [ $? -eq 0 ]; then echo "Appium REST http interface listener started on 0.0.0.0:4723"; break; else echo "Waiting for appium server to start. Sleeping for 1 second"; sleep 1; start_appium_timeout=$((start_appium_timeout+1)); fi; done; test: commands: # Your test package is downloaded in $DEVICEFARM_TEST_PACKAGE_PATH so we first change directory to that path. - echo "Navigate to test package directory" - cd $DEVICEFARM_TEST_PACKAGE_PATH # 1. Your testng.xml is inside the test jar after packaging step. Unzip it using commands: - echo "Unzipping TestNG tests jar" - unzip *-tests.jar # 2. Run your TestSuite by specifying the unzipped testng.xml using commands: - ls -ltr - which appium - appium -v - pwd - node -v - appium -v - which node - echo $DEVICEFARM_LOG_DIR - echo "Start Appium TestNG test" - java org.testng.TestNG -d $DEVICEFARM_LOG_DIR/test-output testng_android.xml ``` Error Log: ``` [DeviceFarm] echo "Start Appium TestNG test" Start Appium TestNG test [DeviceFarm] java org.testng.TestNG -d $DEVICEFARM_LOG_DIR/test-output testng_android.xml log4j:WARN No appenders could be found for logger (mobile.common.filereader.ConfigFileReaderUtils). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. [TestNG] Running: /tmp/scratchDVpVKr.scratch/test-packagemJj_ph/testng_android.xml =============================================== Android Regression Tests Total tests run: 2, Failures: 0, Skips: 2 Configuration Failures: 2, Skips: 1 =============================================== ``` https://us-west-2.console.aws.amazon.com/devicefarm/home?region=us-east-1#/mobile/projects/e7d85810-369a-443b-ac29-86ab38065b81/runs/6d8ad0d2-394c-4de5-898a-eed8e816745c/jobs/00000 Could someone please help me out ? Regards, Sekar
3
answers
0
votes
42
views
asked 4 months ago

Appium WebDriverIO Node.js tests on Device Farm (iOS): ECONNRESET error

Hi, I'm getting the following error every time I try to run my Appium JS tests on iOS devices in AWS Device Farm: **WARN webdriver: Request failed with status 500 due to An unknown server-side error occurred while processing the command. Original error: Failed to receive any data within the timeout: 5000** For the following 2 attempts I get: **ERROR webdriver: RequestError: read ECONNRESET [0-0] at ClientRequest.<anonymous> (/private/tmp/scratchmnNKi2.scratch/test-packagecg02Ek/node_modules/webdriverio-tests/node_modules/got/dist/source/core/index.js:962:111) ** I tried with different Appium versions (1.14.2, 1.18.0, 1.19.0, even installing the latest 1.22.2 manually) as well as various iOS devices. Nothing helps nor changes the outcome. The app .ipa file is valid as I checked it earlier in manual connection sessions and it gets installed every time. So looks like some kind of a connection issue. The same tests work locally. My current desired capabilities look like this (although I also tried to run the tests *without any and got the same result*): ` { platformName: 'iOS', maxInstances: 1, 'appium:automationName': 'XCUITest', 'appium:noReset': true, 'appium:newCommandTimeout': 240 }` Shared capabilities look like this: exports.config = { // // ==================== // Runner Configuration // ==================== runner: 'local', path: '/wd/hub', port: 4723, specs: ['./specs/**/*.js'], // Patterns to exclude. exclude: [ // 'path/to/excluded/files' ], maxInstances: 1, logLevel: 'info', bail: 0, baseUrl: 'localhost', waitforTimeout: 20000, connectionRetryTimeout: 120000, connectionRetryCount: 3, framework: 'mocha', reporters: ['spec'], mochaOpts: { ui: 'bdd', timeout: 200000 //retries: 2 }, afterTest: async function (test, context, { error, result, duration, passed, retries }) { // take a screenshot anytime a test fails and throws an error if (!passed) { const testName = test.title.toString().split(' ').join('-') await driver.saveScreenshot(`./Failure_Screenshot_${testName}.png`) } } } Any help would be appreaciated as this error is not descriptive at all.
0
answers
0
votes
9
views
asked 4 months ago

DVTErrorPresenter: Unable to load simulator devices in Device Farm

Hello everyone, I'm getting this error to try run ios tests on device farm: DVTErrorPresenter: Unable to load simulator devices in Device Farm Used tools: Appium version: 1.22.0 ios version: 15.x Link of run: https://us-west-2.console.aws.amazon.com/devicefarm/home?region=us-east-2#/mobile/projects/a5325ea5-f090-4ac3-aabb-dcec96a31cd4/runs/7aba46fc-69db-4e2f-8170-93cb0115639d/jobs/00000 Logs: ``` [DeviceFarm] export TEST_PLATFORM=ios [DeviceFarm] export EXECUTION_ENVIRONMENT=AWS [DeviceFarm] export SLACK_SOS_FILE=/tmp/slackMSG.tmp [DeviceFarm] rm -f $SLACK_SOS_FILE [DeviceFarm] echo "Start Appium TestNG test" Start Appium TestNG test [DeviceFarm] java -Djdk.tls.client.protocols=TLSv1.2 -javaagent:dependency-jars/aspectjweaver-1.9.5.jar -Dallure.results.directory=/tmp/allure-results org.testng.TestNG -d $DEVICEFARM_LOG_DIR/test-output testng.xml WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.codehaus.groovy.vmplugin.v7.Java7$1 (file:/private/tmp/scratchXJtgqt.scratch/test-packagebB21R6/dependency-jars/groovy-2.5.8.jar) to constructor java.lang.invoke.MethodHandles$Lookup(java.lang.Class,int) WARNING: Please consider reporting this to the maintainers of org.codehaus.groovy.vmplugin.v7.Java7$1 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release [INFO ] ***oo try to write fileName: /tmp/slackMSG.tmp text: https://us-west-2.console.aws.amazon.com/devicefarm/home?region=us-west-2#/projects/a5325ea5-f090-4ac3-aabb-dcec96a31cd4/runs/7aba46fc-69db-4e2f-8170-93cb0115639d [com.mach.core.util.FileUtil.writeFile(FileUtil.java:44)] [13:26:27,817] [0] [INFO ] ***oo capabilities from java: Capabilities {appPushTimeout: 1000, automationName: XCUITest, deviceName: 00008110-001A75102604801E, newCommandTimeout: 420, platformName: iOS, platformVersion: 15.1, updatedWDABundleId: com.facebook.WebDriverAgent..., useNewWDA: true} [com.mach.core.config.driver.AppiumDriverFactory.getIOSCapabilities(AppiumDriverFactory.java:165)] [13:26:27,963] [146] [ERROR] ***** check the capabilities, e: [com.mach.core.config.driver.AppiumDriverFactory.getIOSDriver(AppiumDriverFactory.java:122)] [13:27:20,945] [53128] org.openqa.selenium.SessionNotCreatedException: Unable to create a new remote session. Please check the server log for more details. Original error: An unknown server-side error occurred while processing the command. Original error: Unable to launch WebDriverAgent because of xcodebuild failure: xcodebuild failed with code 65 xcodebuild error message: 2022-02-02 13:27:10.270 xcodebuild[1191:8716] DVTErrorPresenter: Unable to load simulator devices. Domain: DVTCoreSimulatorAdditionsErrorDomain Code: 3 Failure Reason: The version of the CoreSimulator framework installed on this Mac is out-of-date and not supported by this version of Xcode. Recovery Suggestion: Please ensure that you have installed all available updates to your Mac's software, and that you are running the most recent version of Xcode supported by macOS. -- CoreSimulator is out of date. Current version (757.5.0) is older than build version (776.3.0). Domain: DVTCoreSimulatorAdditionsErrorDomain Code: 3 -- 2022-02-02 13:27:10.270 xcodebuild[1191:8716] iOSSimulator: [SimServiceContext sharedServiceContextForDeveloperDir:error:] returned nil (Error Domain=DVTCoreSimulatorAdditionsErrorDomain Code=3 "CoreSimulator is out of date. Current version (757.5.0) is older than build version (776.3.0)." UserInfo={NSLocalizedDescription=CoreSimulator is out of date. Current version (757.5.0) is older than build version (776.3.0).}). Simulator device support disabled. Command line invocation: /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild test-without-building -project /usr/local/avm/versions/1.22.0/node_modules/appium/node_modules/appium-webdriveragent/WebDriverAgent.xcodeproj -scheme WebDriverAgentRunner -derivedDataPath /tmp/scratchXJtgqt.scratch/DerivedDatakuxIoL -destination id=00008110001A75102604801E IPHONEOS_DEPLOYMENT_TARGET=15.1 GCC_TREAT_WARNINGS_AS_ERRORS=0 COMPILER_INDEX_STORE_ENABLE=NO User defaults from command line: IDEDerivedDataPathOverride = /tmp/scratchXJtgqt.scratch/DerivedDatakuxIoL IDEPackageSupportUseBuiltinSCM = YES Build settings from command line: COMPILER_INDEX_STORE_ENABLE = NO GCC_TREAT_WARNINGS_AS_ERRORS = 0 IPHONEOS_DEPLOYMENT_TARGET = 15.1 2022-02-02 13:27:12.088 xcodebuild[1191:8717] DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/DVTiOSFrameworks/DVTiOSFrameworks-19114/DTDeviceKitBase/DTDKRemoteDeviceData.m:373 Details: (null) deviceType from 00008110001A75102604801E was NULL when -platform called. Object: <DTDKMobileDeviceToken: 0x7fbc90f8c120> Method: -platform Thread: <NSThread: 0x7fbc8ec124e0>{number = 3, name = (null)} Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide. 2022-02-02 16:27:19.723982-0500 WebDriverAgentRunner-Runner[417:15887] Running tests... 2022-02-02 16:27:19.726461-0500 WebDriverAgentRunner-Runner[417:15887] Unable to load configuration data from specified path /; error: The file “System” couldn’t be opened. 2022-02-02 16:27:19.726518-0500 WebDriverAgentRunner-Runner[417:15887] XCTRunner Arguments: ( "/var/containers/Bundle/Application/3B1C00BC-8B46-437E-923A-C3A20F6DA262/WebDriverAgentRunner-Runner.app/WebDriverAgentRunner-Runner" ) 2022-02-02 16:27:19.726621-0500 WebDriverAgentRunner-Runner[417:15887] XCTRunner Environment: { "CA_ASSERT_MAIN_THREAD_TRANSACTIONS" = 0; "CA_DEBUG_TRANSACTIONS" = 0; "CFFIXED_USER_HOME" = "/private/var/mobile/Containers/Data/Application/3CE450E6-4DEF-46F3-BB9C-ACB104BA7E97"; HOME = "/private/var/mobile/Containers/Data/Application/3CE450E6-4DEF-46F3-BB9C-ACB104BA7E97"; LOGNAME = mobile; "MJPEG_SERVER_PORT" = ""; "MTC_CRASH_ON_REPORT" = 1; NSUnbufferedIO = YES; "OS_ACTIVITY_DT_MODE" = YES; PATH = "/usr/bin:/bin:/usr/sbin:/sbin"; "RUN_DESTINATION_DEVICE_ECID" = 7447061612232734; "RUN_DESTINATION_DEVICE_NAME" = PDX640550096; "RUN_DESTINATION_DEVICE_PLATFORM_IDENTIFIER" = "com.apple.platform.iphoneos"; "RUN_DESTINATION_DEVICE_UDID" = 00008110001A75102604801E; SHELL = "/bin/sh"; "SQLITE_ENABLE_THREAD_ASSERTIONS" = 1; TMPDIR = "/private/var/mobile/Containers/Data/Application/3CE450E6-4DEF-46F3-BB9C-ACB104BA7E97/tmp/"; "UPGRADE_TIMESTAMP" = 1643837138604; USER = mobile; "USE_PORT" = 8100; "WDA_PRODUCT_BUNDLE_IDENTIFIER" = "com.facebook.WebDriverAgentRunner"; XCTestBundlePath = "PlugIns/WebDriverAgentRunner.xctest"; XCTestConfigurationFilePath = ""; XCTestSessionIdentifier = "88DCC108-B122-4D1C-84E4-DA839C9021CD"; "XPC_FLAGS" = 0x0; "XPC_SERVICE_NAME" = "UIKitApplication:com.apple.test.WebDriverAgentRunner-Runner[9ca9][rb-legacy]"; "__CF_USER_TEXT_ENCODING" = "0x1F5:0:0"; } 2022-02-02 13:27:19.643 xcodebuild[1191:8639] [MT] IDETestOperationsObserverDebug: 6.524 elapsed -- Testing started completed. 2022-02-02 13:27:19.643 xcodebuild[1191:8639] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start 2022-02-02 13:27:19.643 xcodebuild[1191:8639] [MT] IDETestOperationsObserverDebug: 6.524 sec, +6.524 sec -- end Test session results, code coverage, and logs: /tmp/scratchXJtgqt.scratch/DerivedDatakuxIoL/Logs/Test/Test-WebDriverAgentRunner-2022.02.02_13-27-13--0800.xcresult Testing failed: WebDriverAgentRunner: WebDriverAgentRunner-Runner (417) encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted. (Underlying Error: The test runner exited with code 1 before checking in. If you believe this error represents a bug, please attach the result bundle at /tmp/scratchXJtgqt.scratch/DerivedDatakuxIoL/Logs/Test/Test-WebDriverAgentRunner-2022.02.02_13-27-13--0800.xcresult)) ** TEST EXECUTE FAILED ** Testing started. Make sure you follow the tutorial at https://github.com/appium/appium-xcuitest-driver/blob/master/docs/real-device-config.md. Try to remove the WebDriverAgentRunner application from the device if it is installed and reboot the device. Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03' System info: host: 'ip-192-168-10-5.us-west-2.compute.internal', ip: 'fe80:0:0:0:14c0:e6ff:c23e:5cb3%en0', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.16', java.version: '12.0.2' Driver info: driver.version: IOSDriver ... ```
1
answers
0
votes
20
views
asked 5 months ago

Device Farm: Appium iOS test never launches app, WebdriverAgent shows error "Failed to get automation session"

Problem: my tests are not running and eventually get terminated. While I see both the app and WDA getting installed in the video, the app will never get launched. Testspec output does not reveal any meaningful info, only shows "Terminated: 15". Reviewing the syslog output, I'm able to see a couple of issues with WDA: ``` WebDriverAgentRunner-Runner(WebDriverAgentLib)[416] <Notice>: Enqueue Failure: Application 'test.bundle.id.here' has not loaded accessibility /Users/saaandr/Downloads/WebDriverAgent-2.20.8/WebDriverAgentRunner/UITestingUITests.m 38 1 ``` and ``` WebDriverAgentRunner-Runner(WebDriverAgentLib)[416] <Notice>: Enqueue Failure: Failed to get automation session for test.bundle.id.here:0: Timed out while requesting automation session for test.bundle.id.here (pid:0) ``` [ARN run](https://us-west-2.console.aws.amazon.com/devicefarm/home?region=us-west-2#/mobile/projects/c248fb2e-1df2-4c2c-8499-5bf7523ce683/runs/4e9ab72e-c9d7-4081-ad7d-9341c4d10eb2): arn:aws:devicefarm:us-west-2:223051165180:run:c248fb2e-1df2-4c2c-8499-5bf7523ce683/4e9ab72e-c9d7-4081-ad7d-9341c4d10eb2 As far as desired capabilities, I am not modifying anything from the default capabilities. Also, the testspec yml uses the latest testspec for iOS (v 7.0) as a starting point, modified only with a custom py.test command. This is the behavior that I see when I choose to run test on an iOS14.0, or 13.3.1 device. Executing the xcodebuild -version command in the install phase of the testspec shows that it is running Xcode 11.7, which was released back in Sept 2020. The test run eventually gets terminated by the WebDriverAgentRunner not being able to find the app running. But when I attempt to run on a device with iOS14.8 or 15.x, the setup fails within 2 minutes, since the app cannot be installed due to a resigning issue, similar to [this post](https://repost.aws/questions/QUy77blDSqQc-I6jnDZfvY5w/i-phone-application-not-installing-on-i-os-14-8#CO4MziupFYRJ6KpGTsnkiqmA). Worth mentioning, this same test runs with no problems on an Android device. Any help is appreciated.
1
answers
0
votes
61
views
asked 5 months ago

AWS Device Farm can not get the correct app activity for Android app to launch app using Appium

Hi, I'm trying to run a small test for an Android app using Appium and TestNG on AWS device farm and I'm facing this problem. As recommendation from AWS, I just kept the desired capabilities empty like this and I could run the test successfully on my local machine ``` @BeforeSuite public void setUpAppium() throws MalformedURLException { final String URL_STRING = "http://127.0.0.1:4723/wd/hub"; URL url = new URL(URL_STRING); DesiredCapabilities capabilities = new DesiredCapabilities(); driver = new AndroidDriver<MobileElement>(url, capabilities); driver.manage().timeouts().implicitlyWait(35, TimeUnit.SECONDS); } ``` Then I followed all the steps in the instruction: uploaded the apk, zip file, etc. to AWS Device farm. And then when I ran the test on AWS, I got this error: > Cannot start the 'com.simplemobiletools.notes.pro' application. Visit https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/android/activity-startup.md for troubleshooting. Original error: Activity name '.com.simplemobiletools.notes.pro.activities.SplashActivity.Grey_black' used to start the app doesn't exist or cannot be launched As the error message, AWS tried to launch the activity ".com.simplemobiletools.notes.pro.activities.SplashActivity.Grey_black" which is kind of weird because when I used the command "adb shell dumpsys window | grep -E 'mCurrentFocus'" to check the app activity then I got this result "com.simplemobiletools.calculator.activities.MainActivity" and I don't know where AWS got that activity. So I guessed because of the wrong activity, appium couldn't start my app and the test couldn't be run on the device farm. I also checked with other apps and I saw the same problem. App activity that I used the adb shell command to check is always different to the app activity AWS got. AWS seems to tend to add the word "Splash" into the app activity and I don't know what it meant I tried this solution from this link "[https://forums.aws.amazon.com/thread.jspa?messageID=959277&tstart=0](https://forums.aws.amazon.com/thread.jspa?messageID=959277&tstart=0)" by adding appActivity and appWaitActivity to the yaml file ``` - echo "Start appium server" - >- appium --log-timestamp --default-capabilities "{\"deviceName\": \"$DEVICEFARM_DEVICE_NAME\", \"platformName\":\"$DEVICEFARM_DEVICE_PLATFORM_NAME\", \"app\":\"$DEVICEFARM_APP_PATH\", \"udid\":\"$DEVICEFARM_DEVICE_UDID\", \"platformVersion\":\"$DEVICEFARM_DEVICE_OS_VERSION\", \"chromedriverExecutable\":\"$DEVICEFARM_CHROMEDRIVER_EXECUTABLE\,\"appActivity\":\"com.simplemobiletools.notes.pro.activities.MainActivity\",\"appWaitActivity\":\"com.simplemobiletools.notes.pro.activities.MainActivity\"}" >> $DEVICEFARM_LOG_DIR/appiumlog.txt 2>&1 & - >- ``` but it didn't work either. Now I get another error "Waiting for appium server to start. Sleeping for 1 second". I tried to find any solution but couldn't find anything Please help me resolve this issue, I really appreciate your help!
1
answers
0
votes
44
views
asked 6 months ago

Unable to connect to another machine from iOS using RemoteWebDriver

Hello everybody. I'm using AWS Device Farm to run my tests. This is web to mobile testing for video calls, where both desktop pc and mobile phone must be used in one framework. I have a problem to connect to my remote machine in test while using iOS, but everything is fine with Android. I have both Android and iOS applications for mobile testing. The steps I do to run tests using AWS device farm: 1. We have a remote machine with open static IP address where I have a selenium-server-standalone started; 2. I put my project to AWS Device Farm -> Mobile device testing project -> Create a new project; 3. I fill out all the blanks, upload my application, select Java Appium TestNG, set configuration, create device pool and launch run; 4. Project goes to AWS Device Farm and while method 'setup' is invokes both the remote machine and selected mobile device and tests run; When I use my Android application, the test is able to connect to my remote machine and then invoke Android phone, then tests run in parallel on both web pc and mobile device. But when I try to do the same thing with iOS application, I have an unknown problem. I do the same steps with Android. So, the difference is only that it is iOS phone. And when I try to connect to my remote machine, the test skips. Without any log or comment...just skips and that's it. The way I connect to my machine from AWS Device farm mobile project: @BeforeTest public void setUp() { //web DesiredCapabilities dc = new DesiredCapabilities(); dc.setBrowserName("chrome"); dc.setPlatform(Platform.ANY); URL remoteHostURL = new URL("http://x.x.x.x:4444/wd/hub"); DRIVER_WEB.set(new RemoteWebDriver(remoteHostURL, dc)); //mobile capabilities = CapabilityManager.getAndroidCapabilities(); DRIVER_MOBILE.set(new AppiumDriver<MobileElement>(remoteAppiumHostURL, capabilities)); ... } What could cause this problem? Cos it works only for Android, but doesn't work for iOS. I'd be very thankful to get any help from you!
1
answers
0
votes
3
views
asked a year ago

WebDriver Instance for mobile web testing

I'm working on adapting functional tests of a web to be able to use Device Farm as the device pool for testing in mobile devices. The tests are written in Java, using TestNG and Appium, and i have no problems launching them in desktop browsers locally or in my android phone through a local installation of Appium. I have adapted the pom.xml following the guidelines in <https://docs.aws.amazon.com/devicefarm/latest/developerguide/test-types-appium.html> , but i haven't found anything in the documentation stating how i should instantiate WebDriver. I have also reviewed and tested with the method to instantiate it as a RemoteWebDriver using the sdk like this: String myProjectARN = "arn:evicefarm:us-west-2:XXXXXXXXXX:testgrid-project:XXXXXXXX"; DeviceFarmClient client = DeviceFarmClient.builder() .region(Region.US_WEST_2) .build(); CreateTestGridUrlRequest request = CreateTestGridUrlRequest.builder() .expiresInSeconds(300) .projectArn(myProjectARN) .build(); CreateTestGridUrlResponse response = client.createTestGridUrl(request); URL testGridUrl = new URL(response.url()); WebDriver driver = new RemoteWebDriver(testGridUrl, DesiredCapabilities.chrome()); This works fine for testing in desktop environments, but if i try to adapt it to android environment, i get the following error: \[TestNG] software.amazon.awssdk.services.devicefarm.model.DeviceFarmException: User: arn:aws:sts::XXXXXXXXXXXXX:assumed-role/EC2DeviceHostRole/XXXXXXXXXXXXXXXX is not authorized to perform: devicefarm:CreateTestGridUrl on resource: arn:aws:devicefarm:us-west-2:XXXXXXXXXXXXX:project:XXXXXXXXXXXXXXXXXXXXXXXXX (Service: DeviceFarm, Status Code: 400, Request ID: XXXXXXXXXXXXXXXXXXXXXX, Extended Request ID: null) How should WebDriver be instantiated for mobile tests? My goal is to run this tests both in Android and iOS devices.
2
answers
0
votes
23
views
asked a year ago

App activity is never started the app is running on the screen record

Hi, I am trying to run test on Android app with Appium and TestNG. At first I used empty desired capabilities but then I discovered that adding following caps helped to certain users on this forum: capabilities.setCapability("appPackage", "com.everfx"); capabilities.setCapability("appActivity", "com.zoontek.rnbootsplash.RNBootSplashActivity"); capabilities.setCapability("appWaitPackage", "com.everfx"); capabilities.setCapability("appWaitActivity", "com.zoontek.rnbootsplash.RNBootSplashActivity"); capabilities.setCapability("appWaitDuration", "50000"); It is interesting, because I thought that AWS Device Farm is overriding any capabilities that appium server is receiving. Unfortunately it didn't help and I am still received the same error: **Failed to invoke configuration method test.BaseTestClass.setUp:Unable to create a new remote session. Please check the server log for more details. Original error: An unknown server-side error occurred while processing the command. Original error: Cannot start the 'com.everfx' application. Visit https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/android/activity-startup.md for troubleshooting. Original error: 'com.zoontek.rnbootsplash.RNBootSplashActivity' or 'com.everfx.com.zoontek.rnbootsplash.RNBootSplashActivity' never started. Visit https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/android/activity-startup.md for troubleshooting** Then I decided to change "appWaitActivity" to receive ".MainActivity", as Appium might skip seeing splashscreen, however it didn't help either. Service was still expecting to see "com.zoontek.rnbootsplash.RNBootSplashActivity" which might mean that capabilities are not being overridden at all. So question is how to pass capabilities to aws device farm properly? And how to overcome the issue that tests are not seeing app?
7
answers
0
votes
48
views
asked 2 years ago
4
answers
0
votes
10
views
asked 2 years ago

AWS device farm react native appium webdriverio test's not working

Hi, I have created test for React Native application using Appium and WebdriverIO, it&#39;s working fine locally on android emulator and on real device, but it&#39;s not working on aws device farm. This tutorial <https://medium.com/jetclosing-engineering/react-native-device-testing-w-appium-node-and-aws-device-farm-295081129790> I followed to create test. **Issue is** 2020-05-06T14:01:27.388Z INFO webdriver: DATA { using: &#39;accessibility id&#39;, value: &#39;loginEmail&#39; } 2020-05-06T14:01:27.390Z INFO webdriver: COMMAND findElement("accessibility id", "app-root") 2020-05-06T14:01:27.393Z INFO webdriver: \[POST] http://127.0.0.1:4723/wd/hub/session/5a7350a3-e8c2-4c9e-b31a-347ea4defcdb/element 2020-05-06T14:01:27.393Z INFO webdriver: DATA { using: &#39;accessibility id&#39;, value: &#39;app-root&#39; } \[0-0] TypeError in "Simple App testing Valid Login Test" **$(...).setValue is not a function** the same issue is for waitForDisplayed **$(...).waitForDisplayed is not a function** **Device Farm Project Test URL**: <https://us-west-2.console.aws.amazon.com/devicefarm/home?region=us-west-2#/projects/df9dc8c9-3ddc-4822-85ef-1991208ae80e/runs/31e7f665-380e-4e21-bd17-8ff085474ecb> **Below is my package.json file** { "name": "tests", "version": "1.0.0", "description": "", "main": "index.js", "scripts": { "test": "npm install && npx wdio ./wdio.conf.local.js", "package": "npm install && npm-pack-zip" }, "keywords": \[], "author": "", "license": "ISC", "dependencies": { "@wdio/cli": "^6.1.2", "@wdio/local-runner": "^6.1.2", "@wdio/mocha-framework": "^6.1.0", "@wdio/spec-reporter": "^6.0.16", "@wdio/sync": "^6.1.0", "wdio-chromedriver-service": "^6.0.2", "chromedriver": "^81.0.0", "chai": "^4.2.0", "webdriverio": "^6.1.2" }, "devDependencies": { "npm-bundle": "^3.0.3", "npm-pack-zip": "^1.2.7" }, "bundledDependencies": \[ "@wdio/cli", "@wdio/mocha-framework", "@wdio/local-runner", "@wdio/spec-reporter", "@wdio/sync", "webdriverio", "chai", "chromedriver", "wdio-chromedriver-service" ] } **Below is my wdio.config.js file** exports.config = { runner: &#39;local&#39;, specs: \[ &#39;./test/specs/**/*.js&#39; ], exclude: \[ // &#39;path/to/excluded/files&#39; ] maxInstances: 1, capabilities: \[{ maxInstances: 1, appWaitDuration: 100000, appWaitActivity: &#39;*&#39; }], logLevel: &#39;info&#39;, bail: 0, baseUrl: &#39;http://localhost&#39;, path: &#39;/wd/hub&#39;, waitforTimeout: 10000, connectionRetryTimeout: 120000, connectionRetryCount: 3, services: &#39;appium&#39;, port: 4723, framework: &#39;mocha&#39;, reporters: &#39;spec&#39;, mochaOpts: { ui: &#39;bdd&#39;, timeout: 60000 }, } **Below is my yml file install and test phases** phases: install: commands: - npm install -g appium - export APPIUM_VERSION=1.17.0 - avm $APPIUM_VERSION - ln -s /usr/local/avm/versions/$APPIUM_VERSION/node_modules/.bin/appium /usr/local/avm/versions/$APPIUM_VERSION/node_modules/appium/bin/appium.js - cd $DEVICEFARM_TEST_PACKAGE_PATH - echo $DEVICEFARM_TEST_PACKAGE_PATH - npm install test: commands: - echo "Navigate to test source code" - cd $DEVICEFARM_TEST_PACKAGE_PATH/node_modules/* - echo "Start Appium Node test for Qbunk Android" - ls - echo $DEVICEFARM_TEST_PACKAGE_PATH - npm install - echo "Installing wdio" - npm install --save webdriverio @wdio/cli - echo "Installing chai" - npm install --save chai - npx wdio $DEVICEFARM_TEST_PACKAGE_PATH/wdio.conf.js --spec $DEVICEFARM_TEST_PACKAGE_PATH/test/specs/*.js Interesting thing is that this <https://aws.amazon.com/blogs/mobile/testing-mobile-apps-across-hundreds-of-real-devices-with-appium-node-js-and-aws-device-farm/> AWS tutorial I followed and write my test with **wd** working fine on AWS Device farm. Kindly let me know if you need more information. Thanks
1
answers
0
votes
62
views
asked 2 years ago
  • 1
  • 90 / page