Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

(blue star) Zephyr for Jira is now Zephyr Squad!Read more about this.

Redirect
filename
delay0
locationhttps://support.smartbear.com/zephyr-for-jira-cloud/docs/continuous-integration/index.html

About

Continuous Integration (CI) is a widely-adopted software development approach which implies running automated builds and tests frequently, several times a day, ideally after every change made to application sources. This guarantees that every, even minor change in your code is tested thoroughly and doesn’t break existing functionality.

Continuous delivery (CD) is a similar practice that implies that you not only automate test runs, but also automate release processes and is able to deploy your application quickly and easily at any time.

If your company uses the continuous integration (delivery), then most likely, you use CI/CD tools like Jenkins, Bamboo, Team City, Azure DevOps, or others.

Widget Connector
overlayyoutube
_templatecom/atlassian/confluence/extra/widgetconnector/templates/youtube.vm
width300px
urlhttps://www.youtube.com/watch?v=ze14urJppWE&feature=youtu.be
height200px

Why integrate?

You can integrate Zephyr for Jira into your CI/CD workflow. The integration means that you configure CI/CD tasks (also often called builds) to create and run automation tasks and pass results of automated tests to test execution cycles in your instance of Zephyr for Jira.

How to integrate

1. Prepare integration script

To integrate CI systems with Zephyr for Jira, you use special Shell script that work with Zephyr for Jira through API.
We provide samples .bat and .sh scripts files to demonstrates how to create and run an automated task through API, and how to update it.

You can easily adopt these sample scripts to your needs: all you have to do is to replace constants in the script with values relevant to your projects.
For detailed information on changes and for download links, see --

(blue star) Integration Script Explained

2. Configure your CI jobs

After you prepared the script, you can call it from your CI jobs. The following topics explain how you can do this from popular CI/CD systems:

(blue star) Jenkins

(blue star) Bamboo

See Also

Test Automation