aws-device-farm

AWS Device Farm.How can i save the custom report being generated after the test case into my local space

♀尐吖头ヾ 提交于 2019-12-11 02:37:57
问题 I am working with AWS device farm.My test script when run on my local system works as expected and generates a report in my local system at specified path.Now when i run the code in the device farm the report does not get generated.Am i missing something? This is my test code to write the test cases to a html report. package testOutput; import java.io.File; import java.io.FileNotFoundException; import java.io.FileOutputStream; import java.io.IOException; import java.io.OutputStream; import

Appium test doesn't even start on AWS DeviceFarm

早过忘川 提交于 2019-12-08 13:02:43
问题 I have run somel iOS Appium tests (Java TestNG) on iOS devices for my app. Some tests don't even install the app, on six or seven out of 22 devices. All with the exact same error about not creating a session: Trying to execute simple Appium Driver Failed to invoke configuration method scenarios.ScreenshotsAppiumTest.setUp: It is impossible to create a new session because 'createSession' which takes HttpClient, InputStream and long was not found or it is not accessible The test works and

Access additional test files for Appium tests on AWS device farm

£可爱£侵袭症+ 提交于 2019-12-06 12:32:42
I am running Appium tests with JUnit on AWS device farm. Is there a way to upload additional test files and access them from within my code? So basically, can I access the file system of the container that runs the Appium tests? I have the necessary files within my JAR file (which is inside a zip as per AWS requirements) but I'm not sure if and where AWS extracts the files from this JAR during the test run (probably not). There is an option called Add extra data which can be used to upload files but I'm not sure how to access them from within my code. The documentation states: For iOS, the

Create Device Pool returning None repsonse - AWSCLI

折月煮酒 提交于 2019-12-05 03:58:39
问题 I am creating a devicepool using AWS CLI as below aws devicefarm create-device-pool --project-arn arn:aws:devicefarm:us-west-2:826601527641:project:90cbdcb5-4dab-438e-8ff6-e0680b376619 --name Devicepool_viago_android_0310201614131457612089 --description Devicepool_viago_android_0310201614131457612089 --rules '[{"attribute": "ARN", "operator": "EQUALS", "value":"arn:aws:devicefarm:us-west-2::device:C66D1BC946634884A129A4456EBA0239"}]' I want to create a device pool with only one device. I am

Create Device Pool returning None repsonse - AWSCLI

一曲冷凌霜 提交于 2019-12-03 21:11:42
I am creating a devicepool using AWS CLI as below aws devicefarm create-device-pool --project-arn arn:aws:devicefarm:us-west-2:826601527641:project:90cbdcb5-4dab-438e-8ff6-e0680b376619 --name Devicepool_viago_android_0310201614131457612089 --description Devicepool_viago_android_0310201614131457612089 --rules '[{"attribute": "ARN", "operator": "EQUALS", "value":"arn:aws:devicefarm:us-west-2::device:C66D1BC946634884A129A4456EBA0239"}]' I want to create a device pool with only one device. I am getting error as below A server error (InternalFailure) occurred when calling the CreateDevicePool

Building XCTest UI tests for AWS Device Farm

爷,独闯天下 提交于 2019-12-03 05:13:55
问题 I'm trying to set up our iOS XCUITests to run on AWS Device Farm, but it seems no matter how I build and upload them, the tests will not run. They execute and pass when run locally in XCode, but do not run on AWS Device Farm. I've set up the absolute simplest app I can manage to try to isolate this issue. It consists of a single View with a single Label, and a UI Test which verifies that the label exists. Here is the error that appears in AWS Device Farm's interface. Digging into the log

Can't read properties file in aws device farm

为君一笑 提交于 2019-12-02 01:46:18
问题 My Appium + JUnit tests works perfectly fine locally, but on aws it can not find properties files. My tests are placed under src/test/java and properties files used in tests under src/test/resources/locale . Zip with dependencies content: ├── app-0.1-tests.jar ├── app-0.1.jar └── dependency-jars ├── ... app-0.1-tests.jar content: ├── META-INF │ ├── MANIFEST.MF │ ├── maven │ ├── .... ├── com │ ├── .... └── locale ├── en_EN.properties Unfortunately when I try to load properties files I have an

AWS Device farm seems to be ignoring TestNG annotations

不问归期 提交于 2019-11-29 11:25:14
I have successfully uploaded and run my tests on AWS device farm. Locally, I'm using fun things like @Test(enabled = false, dependsOnGroups = "Login") to mark which tests to run at the time, and what order they should execute. Locally, this all works fine and dandy as expected. The problem happens after I upload the zip of the maven build to device farm and perform a test run. Looking at the logs from device farm, it doesn't care if "enabled" is set to true or false, it'l run things regardless. It also ignores the "group=" and "dependsOnGroups" annotations. This is super important, since all

AWS Device farm seems to be ignoring TestNG annotations

百般思念 提交于 2019-11-28 04:36:46
问题 I have successfully uploaded and run my tests on AWS device farm. Locally, I'm using fun things like @Test(enabled = false, dependsOnGroups = "Login") to mark which tests to run at the time, and what order they should execute. Locally, this all works fine and dandy as expected. The problem happens after I upload the zip of the maven build to device farm and perform a test run. Looking at the logs from device farm, it doesn't care if "enabled" is set to true or false, it'l run things