automation-testers/Kobiton - Execute Appium Test
Github action to execute an Appium script on a Kobiton real device
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Dec 30, 2022
- License
- MIT
Pinned Snippet
uses: automation-testers/-execute-appium-test-github-action@dc09e8c01b6e29f52b7f9fbb9abc99f814f9652d # no releases — HEAD as of 2026-07-11tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| kobi_username | The user in Kobiton | yes | — |
| kobi_api_key | Specific key to access Kobiton API | yes | — |
| executor_url | Kobiton Automation Test Executor URL to perform the test, please contact our Support Team to get this | yes | — |
| executor_username | Kobiton Automation Test Executor username, please contact our Support Team to get this | yes | — |
| executor_password | Kobiton Automation Test Executor password, please contact our Support Team to get this | yes | — |
| git_repo_url | Link to your Git repository | yes | — |
| git_repo_branch | The branch you want to execute automation test with | yes | — |
| git_repo_ssh_key | It is used when your Git repository is private | no | — |
| app_id | App ID or App URL to use in test script, for example 'kobiton-store:123458' | no | — |
| use_custom_device | Check if you want to execute one or some test cases with a specific Kobiton Cloud Device. If you already set your device information in your test script, leave this field unchecked | no | false |
| device_name | Kobiton Device Name | no | — |
| device_platform_version | Kobiton Device platform version | no | — |
| device_platform | Kobiton Device platform | no | — |
| root_directory | Input the root directory of your project | yes | / |
| command | Command lines to install dependencies and execute your automation test script. These commands will run from the root directory of your project (i.e 'mvn test') | yes | — |
| wait_for_execution | Check if you want to release the pipeline to wait until your automation testing is completed or failed, then print out the console log and test result | yes | true |
| log_type | Log type to be showed. Choose Combined to show logs in chronological order (default), or specify a type of log ('output', 'error') | no | combined |
Outputs
no outputs