aws-devicefarm
aws-devicefarm copied to clipboard
realm
Github action for triggering runs on AWS devicefarm
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: realm/aws-devicefarm/create-upload@v1.
Some Tests setup requires the existence of other apps on the device. This PR support the auxiliaryApps configuration parameter which will upload the configured apps prior to the test execution....
> filter -> (string) > The test's filter. https://docs.aws.amazon.com/cli/latest/reference/devicefarm/schedule-run.html Would be great if the test filter could be passed.
## Summary In response to this [Issue](https://github.com/realm/aws-devicefarm/issues/16) about `test-application` is failing without any outputs ## Introduced changes * Add run arn as an output once it becomes available after `scheduleRun`...
I'm currently using `${{ steps.adf.outputs.arn }}` with ```yaml - id: adf name: Amazon Device Farm uses: realm/aws-devicefarm/test-application@v1 with: ... ``` to reconstruct the test run URL to provide feedback to...
How can I get the artifact files when tests fail? These files are just for successful tests: Test spec file.yml Invalid Artifact Logging Warning.txt Customer Artifacts.zip
In my case I need to be able to specify device configuration: `deviceSelectionConfiguration` ```sh DEVICE_CONFIG="billingMethod=UNMETERED,radios={wifi=true,bluetooth=true,nfc=true,gps=true}" # Device configuration if [[ -f "data_arn.txt" ]]; then DEVICE_CONFIG="${DEVICE_CONFIG},extraDataPackageArn=$(cat data_arn.txt)" fi # Execution configuration...
Githubs javascript bindings nowadays support reading booleans via getBooleanInput. Inputs expecting bools should now be marked as such in action.yml, and reading those inputs changed in javascript.
The following code throws an error as `Error: ValidationException: 2 validation errors detected: Value '' at 'appArn' failed to satisfy constraint: Member must satisfy regular expression pattern: ^arn:.+; Value ''...
We could add an array of jobs to the `data.run` output, and an array of suites to `data.run.jobs[]`. This will make it easier to use `download-artifacts` on a specific suite...
