Project Creation & Setup
Last updated
Last updated
After clicking on ‘Device Farm’, the user can click on the ‘New Project’ button located on the top right of the screen to create a new project.
When creating a new project, the user is required to fill out two text fields:
Project name
Project description
After these two fields have been filled out, click on ‘Create Project’.
You Can Edit and Delete the Project
The Application Management screen allows you to effortlessly upload, organize, and manage your application files for testing on our Device Farm SAAS platform. You can upload APK, IPA, APK Set (APKS), and Android App Bundle (AAB) files, ensuring a seamless testing experience across various device configurations.
Our platform supports the following application types:
APK: Android Package files
IPA: iOS Application Archive files
APKS: Android Package Set files
AAB: Android App Bundle files
Application File Uploads:
In the project dashboard, locate the "Application Files" section.
Click on the "Upload File" button to upload your application files.
An Upload Window pop-up will be displayed to choose the file.
Select the file which needs to be uploaded.
Select Application for Tests:
After uploading, you'll see a list of uploaded application files. Keep an eye on the upload status, and if it's initially marked as "processing," refresh the screen periodically.
Continue refreshing the screen until the upload status changes from "processing" to "completed."
Once the status shows as "completed," you're all set to use the uploaded application on the respective devices.
Click here to get more information on using the uploaded applications
Authentication is a critical aspect of securing your Qyrus Device Farm account and ensuring the privacy of your data. Here's how to manage authentication effectively:
Generate Authentication Token:
Project Token :- This will the unique key to represent a Project. This is required to authenticate via Rest Api calls.
User Token :- This will be Unique for every user account for authentication. This is required to authenticate via Rest Api calls.
Copy Token Details:
Once you've generated the token, you'll see the token details displayed.
This token value, will be required for authentication during automation sessions and for API invocations from the swagger document.
Regenerate Token Details:
To regenerate the token, Click on refresh button highlighted in the image.
Integrations empower you to streamline your testing efforts and collaborate efficiently. By connecting Qyrus Device Farm with your existing tools, you can create a more cohesive and productive testing environment.
To Integrate your Qyrus session with Jira tool :
navigate to device-farm-projects, select project you want integrate with jira tool and click on project setup
Navigate to integration tab in setup page and click on add configuration , this will navigate you to integration page global jira configuration
once in jira configuration page follow the below steps to connect your project to jira.
Enter Configuration Details:
Enter a configuration name to identify this integration.
Provide the valid domain URL of your project management tool.
Generate API Token:
Within your project management tool, generate an API token specifically for integration.
This token will enable communication between the testing platform and your project management tool.Click to generate API Token
Test Connection:
Click the "Test Connection" button to ensure that the testing platform can connect to your project management tool using the provided URL and token.
Select Team, service and project:
Select Team, service and projects which you want to connect with provided jira configuration.
Create/Update Configuration:
If the connection test is successful, Create/Update the integration configuration.
Alternatively user can navigate to jira configuration directly from dashboard as shown below:
Network profiles in Qyrus Device Farm allow you to customize network settings for more realistic testing scenarios. You can configure bandwidth, latency, and packet loss to simulate different network conditions. Here's how to set up and use network profiles:
Create a New Network Profile:
Look for an option to create a new network profile.
Give the profile a descriptive name to easily identify its purpose.
Configure Network Settings:
Within the network profile configuration, adjust the following settings:
Bandwidth: Set the desired bandwidth speed.
Delay: Define the latency value for the network.
Packet Loss: Specify the packet loss percentage.
Save the Profile:
After configuring the network settings, save the profile for future use.
Simulate Sessions with Network Profiles:
When initiating test sessions, you'll have the option to select a network profile.
Choose the appropriate network profile based on the desired testing conditions.
Observe Realistic Network Behavior:
During test sessions, the selected network profile will be applied.
This allows you to observe how your application performs under various network conditions.
Edit or Delete Profiles:
If needed, you can edit or delete existing network profiles.
Editing lets you adjust settings, while deletion removes the profile from your options.
Remote devices provide the flexibility to execute tests on various devices remotely, ensuring broad coverage and efficient testing. Remote devices play a crucial role in your test automation process. They allow you to generate JSON data for automation sessions and connect devices to test automation code.
Select the Device:
Select the device to Automate.
Remote Device Info will be generated.
Select Application File:
Based on the previously configured application files, you can choose the appropriate file for your automation session.
Clicking "Copy URL" generates an endpoint URL necessary for your automation code.
Integrate JSON Data:
Copy the JSON data generated in step 3 and integrate it into your test automation code.
This will establish a connection between your local environment and the remote devices.
Swagger documentation provides a comprehensive overview of all available functionality in the Qyrus Device Farm exposed as APIs. This documentation allows developers to understand and interact with the APIs effectively. Here's how to access and utilize the Swagger documentation:
Explore API Endpoints:
In the Swagger documentation, you'll find a list of all API endpoints categorized by functionality.
Each endpoint is accompanied by details such as its HTTP methods, parameters, request bodies, and response structures.
Understand Functionality:
Read the descriptions provided for each API endpoint to understand its intended functionality and usage.
Review any sample request and response payloads to grasp the expected data format.
Parameters
projectId :- Project Token
sessionId :- At the time of running Automation Session, sessionId can be retrived by using driver.getSessionId()
;
profileName :- Network ProfileName
Custom :- User token
Test Endpoints:
Swagger documentation often provides a feature to test API endpoints directly from the documentation.
Utilize this testing functionality to interact with the APIs and observe their behavior.