Bamboo is a continuous-integration, deployment, and delivery tool from Atlassian that integrates incredibly well with Jira.
TM4J's Bamboo integration enables you to automate tests outside Jira, run them in Bamboo during the CI/CD pipeline, and have results sent back to TM4J for reporting and tracking.
To initiate the TM4J integration with Bamboo, an admin must navigate to Bamboo's Global Variables and set variable names and values for both jira_user and jira_password.
Prior to executing tests, Cucumber users with gherkin definitions in Test Management for Jira should create a script task and add the following code to enable feature files to be downloaded from TM4J. When you add the code, replace the PROJECT_KEY and JIRA_URL variables with your actual information. Optionally, you can replace the TARGET_PATH, ZIP_FILE, and AUTO_CREATE_TEST_CASES variables with your information, as well.
To transfer your test-execution results from Bamboo back to TM4J, you need to create a final script task in the job where you want to report the test results.
Depending on if you use Cucumber or JUnit, add one of the following code sets, and remember to replace the PROJECT_KEY and JIRA_URL variables with your actual information. Optionally, you can replace the PATH_FILE, ZIP_FILE, and AUTO_CREATE_TEST_CASES variables with your information, as well.
When executed properly, the script runs after the testing concludes. Regardless of whether the tests pass or fail, the build completes, and the test results are published to TM4J.
This task describes how to apply scripts in Bamboo for the TM4J integration.