How to integrate real-device testing into a Bamboo pipeline

Reading Time : 3 min read
Integrate Real Device Testing

What Is Bamboo?

Bamboo is a continuous integration (CI) server that can be used to automate the release management for a software application, creating a continuous delivery pipeline.

What does this mean?

CI is a software development methodology in which a build, unit tests, and integration tests are performed, or triggered, whenever code is committed to the repository, to ensure that new changes integrate well into the existing code base. Integration builds provide early ‘fail fast’ feedback on the quality of new changes.

Bamboo assists software development teams by providing:

  • automated building and testing of software source-code status.
  • updates on successful and failed builds.
  • reporting tools for statistical analysis.

Install and Configure Bamboo

We can download and try Bamboo free for 30 days with unlimited users at https://www.atlassian.com/software/bamboo/download. When you set up Bamboo successfully, we can move to the next part.

Set up a Bamboo project with Javascript samples

As you know, Bamboo is also one of the famous CI/CD tools. So, in this article, I will teach you how to trigger automation test with Kobiton devices through Bamboo. The language that I use to write scripts is javascript. You can refer to the source code at https://github.com/kobiton/samples.git. Please see the details below:

Create a New Project

  1. From the top menu bar, click Create->Create project
    • Project name: The name of your project
    • Project key: The key of your project
  2. Click Save

Create a New Plan

  1. From the top menu bar, click Create->Create plan
    • Plan name: The name of your plan
    • Plan key: The key of your planBamboo project configuration screen showing the Kobiton Bamboo Integration project, plan name setup, plan key field, and build plan creation settings.
  2. Link repository to a new build plan
  3. Then, click Configure plan to finish this part

Create Tasks

  1. Click Add task
  2. Enter Script to search Task types
  3. Select Script
  4. Enter Task descriptionBamboo build plan task configuration screen showing a script task setup with shell interpreter options, script location settings, and a code editor for entering automation scripts.
  5. Copy the snippet code below and paste into Script body
  6. Click Save
  7.  Click Save and Continue

cd javascript && npm install
KOBITON_USERNAME=${bamboo.KOBITON_USERNAME} KOBITON_API_KEY=${bamboo.KOBITON_API_KEY} npm run android-web-test
KOBITON_USERNAME=${bamboo.KOBITON_USERNAME} KOBITON_API_KEY=${bamboo.KOBITON_API_KEY} npm run android-app-test
KOBITON_USERNAME=${bamboo.KOBITON_USERNAME} KOBITON_API_KEY=${bamboo.KOBITON_API_KEY} npm run ios-web-test
KOBITON_USERNAME=${bamboo.KOBITON_USERNAME} KOBITON_API_KEY=${bamboo.KOBITON_API_KEY} npm run ios-app-test

Add variables

  1. Select Variables tab
  2. Add two variables

    • KOBITON_API_KEY
    • KOBITON_USERNAMEBamboo CI/CD Variables page showing configuration of environment variables, including KOBITON_API_KEY and KOBITON_USERNAME, used to authenticate automated mobile testing workflows with Kobiton.

Enable Plan

  1. On the right corner, select Actions drop-down
  2. Choose Enable plan

Dropdown menu in Bamboo displaying plan management options, including enabling a build plan, creating issues, configuring plans, modifying labels, and marking plans as favorites.

Run Plan

  1. Go to Build -> All build plans
  2. Click created plan link
  3. Click Run -> Run Plan option, as shown below.

Bamboo build interface showing the Run menu expanded with options to start a plan run or launch a customized build.

  1. If the run is successful, then it shows a message in green color.Bamboo build results page showing a successful Kobiton integration test run, including build status, duration, agent details, and test summary information.
  2. If the build is failed, then it shows a message in red color.Screenshot of an Atlassian Bamboo build results page for a Kobiton Bamboo Integration project. The page shows Build #2 with a red failure banner indicating the build failed during a manual run. The Build Result Summary section displays build details such as completion time, duration, agent, and revision information. A warning message at the bottom states “No failed tests found, a possible compilation error occurred.” The right panel shows responsibility management options, indicating that no user has yet taken responsibility for the failed build. This screen illustrates a CI/CD pipeline build failure related to compilation rather than test execution.

Reports

  • We can view the report Details by clicking on the Running JobScreenshot of an Atlassian Bamboo build results page for a Kobiton integration project. The build is marked as successful, with a green status indicator showing that automated tests completed without errors. The page includes build details such as execution time, agent information, source code revision, and test results. Tabs for Summary, Tests, Commits, Artifacts, Logs, and Metadata are available, illustrating a successful CI/CD pipeline execution integrated with mobile test automation.
  • We can also view the overview by clicking on your plan, it lists out all passed/ failed jobsBamboo build dashboard showing a Kobiton integration plan summary with build history, success rate statistics, and recent automated test run results.
  • Or access https://portal.kobiton.com/sessions to get your test sessionsScreenshot of the Kobiton test session dashboard showing completed automation test sessions across iOS and Android devices, including OS versions, device models, session details, and filtering options.

Interested in Learning More?

Subscribe today to stay informed and get regular updates from Kobiton

Ready to accelerate delivery of
your mobile apps?

Request a Demo