- Newest
- Most votes
- Most comments
Hi,
I tried to set the ARN for the YAML file manually during my test scheduling but the test will not be executed on this custom environment. Is there an additional setting to enable the custom env?
Only setting the TestSpec file seems not to work.
Norman
Hello,
When using our CreateUpload APIs to upload a app, test app, or yaml file to your project, the response will return an ARN in the object that you can then use for later runs. This way, you will not have to re-upload the files for every scheduled run. To see if the upload has succeeded, you can call GetUpload and see if the status has been set to SUCCEEDED. If its in status FAILED, you can view the metadata of that Upload object to see troubleshooting tips on how to fix the issue.
You can delete uploads with our DeleteUpload API.
CLI Doc links
CreateUpload: https://docs.aws.amazon.com/cli/latest/reference/devicefarm/create-upload.html
GetUpload: https://docs.aws.amazon.com/cli/latest/reference/devicefarm/get-upload.html
DeleteUpload: https://docs.aws.amazon.com/cli/latest/reference/devicefarm/delete-upload.html
Hello,
Can you add a bit more detail on which exception message you are getting?
Hi,
I was now able to specify an existing Test Spec ARN to my TestRunRequest. It is working properly.
Thanks for the hint with the delete of the yaml - will try to implement it as well.
I checked the ARN with get-upload to be sure if the Arn and result was the right one.
In my code I specify the TestSpecArn like the following into my "ScheduleRunRequest":
myRunRequest.Test.TestSpecArn = "arn:aws:devicefarm:.........."
Execution works fine in custom env now.
Thanks
Norman
Relevant content
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a month ago