Run an automation test using Bitrise Learn how to run an automation test using Bitrise. Before you start You’ll need to complete the following: Create a Bitrise workflow. Upload a project to your cloud VCS. Get your credentials Some credentials can be added while you’re configuring your pipeline.yml, but others are easier to get beforehand. Save the following credentials to a secure location so you can easily add them to your pipeline.yml later: Kobiton API key: get API key values from your list of Kobiton API keys. Executor server credentials: N/A Cloud repository credentials: get the URL and SSH key for the project you uploaded. Add the workflow Open Bitrise and select Workflows. Next to your workflow, select the edit icon. Select the + icon. Use the search bar to find and add Execute Automation Test in Kobiton. Add your credentials You’ll be redirected to the workflow editor. In the Input variables pane, use your credentials to fill out all the following fields: Kobiton Username Kobiton API Key Executor Server URL Executor Username Executor Password Git Repository URL Git Repository Branch Git Repository SSH Key Configure your build steps Build steps are project-specific, so fill out the remaining fields in the Input variables pane to best meet your project needs: Property Description Root Directory (Required) The relative path to your project’s root directory, such as /. Command (Required) The command(s) used to install your project dependencies and run your test scripts. App ID When testing your app (rather than your website), assign the app’s existing Kobiton ID. Use Custom Device Set to true if you’d like to test a specific device. Device Name If use-custom-device is set to true, set to the device’s name. Device Platform Version If use-custom-device is set to true, set to the device’s platform version. Device Platform If use-custom-device is set to true, set to the device’s platform. Wait for Execution Set to true if you want the pipeline to wait until the test is complete. Log Type Set to combined for chronological logs, output for output logs, error for error logs. When you’re finished, select Save.