AWS – Device Farms
AWS Integration in Avo Assure
Last updated
AWS Integration in Avo Assure
Last updated
Test scripts of application type - ‘Mobile Apps’ can be executed on the AWS platform by utilizing the AWS service - ‘Device Farm’. This section provides an overview of how execution can be triggered on AWS using Avo Assure.
The following can be the justifications of integrating AWS – Device Farms with Avo Assure:
Test cases created with ease using Avo Assure for mobile applications can be executed on the AWS device farm allowing integration of testing existing test scenarios as and when the mobile application’s development progresses.
Executing on AWS gives abundant access to resources. Using this, the testing of the AUT can be done on devices that the end-users of the AUT use.
The above benefit reaps another advantage – an increase in efficiency of reproducing the defects and in turn fixing them quickly.
If testing on varying device specifications is needed, then AWS is the perfect option as the ‘Device Farm’ service of AWS provides an extensive range of devices.
The following conditions must be met in order to trigger execution on AWS from Avo Assure:
The end-user must have an account in AWS. The account can be created by signing up at ‘https://aws.amazon.com/console/'.
For every new project - the user must sign in to their AWS account and follow the below-mentioned steps:
Search the ‘Services’ section of AWS and Select for ‘Device Farm’, which is a sub-service of ‘Mobile’ services.
2. On selection of ‘Device Farm’. The following screen can be observed:
3. Click on ‘Create a new project’ and enter an appropriate project name.
4. Click on the ‘Create project’ button.
5. Click on the ‘Project settings’ link.
6. Navigate to the ‘Device pools’ tab under the project settings.
7. Click on the ‘Create a new device pool’ button. The following screen will pop up:
8. Enter the appropriate name and description for the device pool.
9. Select the devices needed from the wide range of devices available [prefer devices with ‘Status’ of ‘HIGHLY_AVAILABLE’].
10. Click on the ‘Save device pool’ button.
11. After saving the device pool, click on ‘Done’.
Note:
Multiple device pools can be created for a project.
Device pools are identified by their names. Hence, for the execution of mobile test scenarios on AWS, it is crucial that the proper device pool name is noted.
The device pool belongs strictly to one project, that is, a device pool from one project cannot be accessed by another project.
The project name is also important for the execution of mobile test scenarios on AWS. Hence, the user should make a note of the project name.
3. The access keys provided by AWS are also required. The following section will describe on the process of generating access keys from AWS.
