How to use Kobiton with Travis CI?

Continuous Integration is the practice of merging in small code changes frequently – rather than merging in a large change at the end of a development cycle. The goal is to build healthier software by developing and testing in smaller increments. This is where Travis CI comes in.

As a continuous integration platform, Travis CI supports your development process by automatically building and testing code changes, providing immediate feedback on the success of the change. Travis CI can also automate other parts of your development process by managing deployments and notifications.

 

Prerequisites

• To start using Travis CI, make sure you have:
  • A GitHub or Bitbucket account.
  • Owner permissions for a project hosted on GitHub or Bitbucket.
• Navigate to GitHub and fork Kobiton repository.

 

To get started with Travis CI using GitHub 

1. Go to Travis-ci.com and Sign up with GitHub.
2. Accept the Authorization of Travis CI. You’ll be redirected to GitHub.
3. Click on your profile picture in the top right of your Travis Dashboard, click Settings, and then the green Activate button, and select the repositories you want to use with Travis CI.
4. Or you click the Activate all repositories using GitHub Apps button on the getting started page to just activate all your repos

Configure the environment variables

• Access to Kobiton portal site to get the  USERNAME and API KEY
• Access to https://travis-ci.com/github/{username}/Travis-CI/settings to add two variables KOBITON_USERNAME and KOBITON_API_KEY into the Environment Variables
  

Build the project

• After the Builds on Travis CI are configured mostly through the build configuration stored in the file .travis.yml in your repository, now we can trigger the build and run the test with the Kobiton Cloud devices.
  
• We can see the detailed information about Travis CI’s build.
  
  

Test Results on Kobiton portal

• When you see your test ‘passed’ on Travis CI, you can access https://portal.kobiton.com/login to get your test results.
  
• We can see the session overview for the latest test session.
  
• The HTTP Commands details are also included in the test result.
  
• The video is also captured and uploaded.
  
• The log report includes the device log and the Appium log as well.