{"id":24586,"date":"2023-09-15T09:02:19","date_gmt":"2023-09-15T00:02:19","guid":{"rendered":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/9\/?page_id=24586"},"modified":"2023-09-20T18:35:02","modified_gmt":"2023-09-20T09:35:02","slug":"travis-ci","status":"publish","type":"page","link":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/9\/test-automation\/ci-cd-tools-integration\/travis-ci\/","title":{"rendered":"Integrating with Travis CI"},"content":{"rendered":"

Travis CI<\/a> is a CI\/CD (Continuous Integration and Deployment) tool that helps development teams release code rapidly and automate the build, test, and deployment of their applications. Using Travis CI, engineers can automate their entire testing suite for new commits, reducing the potential for human error.<\/p>\n

An everyday use case for Travis CI is building and testing your application whenever code changes are submitted. To take full advantage of TestRail and manage all your test cases and test results, both manual and automated, you can send your automated test results directly from Travis CI to TestRail. This article will explore how to easily use Travis CI and the TestRail CLI to accomplish this task.<\/p>\n

\n

[et_pb_text admin_label=”Note” _builder_version=”4.4.2″ background_color=”#F0F8FF” hover_enabled=”0″ border_width_all=”1px” border_color_all=”#b0c4de”]<\/p>\n

Please note that the TestRail CLI requires that a compatible JUnit XML report<\/strong> is generated by your test automation framework.<\/p>\n

[\/et_pb_text]<\/p>\n<\/div>\n

Using the TestRail CLI in Travis CI builds<\/h2>\n

Automated processes can be configured in Travis CI using a .travis.yml<\/code> file. The .travis.yml<\/code> file describes the build process. These YAML files allow you to specify your build process in a structured manner. Under .travis.yml<\/code>, you can specify a default build environment and a default set of phases for each programming language.<\/p>\n

The easiest way to integrate TestRail with Travis CI is by configuring your .travis.yml<\/code> to use the TestRail CLI to send automated test results to TestRail. Below is a sample of how a workflow file using the TestRail CLI to send test results to TestRail would look like.<\/p>\n

dist: xenial\njobs:\n  include:\n    - stage: Run tests and upload results to TestRail\n      language: python\n      python: 3.9-dev\n      addons:\n        chrome: stable\n      script:\n        - mvn clean compile test\n      after_script:\n        - pip install trcli\n        - trcli -y\n           -h https:\/\/INSTANCE.testrail.io\/\n           --project \"PROJECT NAME\"\n           -u USER_EMAIL\n           -p PASSWORD\n           parse_junit\n           --title \"Automated Tests from Travis workflow\"\n           --run-description $TRAVIS_JOB_WEB_URL\n           -f \".\/target\/surefire-reports\/TEST-TestSuite.xml\"<\/pre>\n
A build in Travis CI is a sequence of stages<\/a>. Each stage consists of a sequence of jobs. Each stage in Travis CI is executed in a single unit within a fresh container or a virtual machine.<\/p>\n
Breaking down the .travis.yml<\/code>, we notice some interesting facts.<\/p>\n