Skip to end of metadata
Go to start of metadata

Bamboo is a continuous-integration, deployment, and delivery tool from Atlassian that integrates incredibly well with Jira.

Test Management for Jira’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.

Prerequisite

Windows users must download and install Curl and 7-zip and add both system paths to their machines. More information about how to update system path variables is here.

Before You Test: Set Global Variables

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.

Before You Test: Download Feature Files

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_PATHZIP_FILE, and AUTO_CREATE_TEST_CASES variables with your information, as well.

Windows: Download Feature Files from TM4J
set USER=%bamboo_jira_user%
set PASSWORD=%bamboo_jira_password%
set BUILD_DIR=${bamboo.build.working.directory}
set TARGET_PATH="src/test/resources/features"
set ZIP_FILE="bddfile.zip"


set PROJECT_KEY="WEB"
set JIRA_URL="http://localhost:2990"

echo "Clean target path"
rm -rf %BUILD_DIR%/%TARGET_PATH%
mkdir -p %BUILD_DIR%/%TARGET_PATH%

echo "Downloading feature files"
curl -u %USER%:%PASSWORD% %JIRA_URL%/jira/rest/atm/1.0/automation/testcases?tql="testCase.projectKey='%PROJECT_KEY%'" --output %BUILD_DIR%/%TARGET_PATH%/%ZIP_FILE%

echo "Unzipping feature files"
7z e -aoa %BUILD_DIR%/%TARGET_PATH%/%ZIP_FILE% -d %BUILD_DIR%/%TARGET_PATH%

echo "Finished"


Linux: Download Feature Files from TM4J
USER=$bamboo_jira_user
PASSWORD=$bamboo_jira_password
BUILD_DIR="${bamboo.build.working.directory}"
TARGET_PATH="src/test/resources/features"
ZIP_FILE="bddfile.zip"

JIRA_URL="http://localhost:2990"
PROJECT_KEY="WEB"

echo "Clean target path"
rm -rf $BUILD_DIR/$TARGET_PATH
mkdir -p $BUILD_DIR/$TARGET_PATH

echo "Downloading feature files"
curl -u $USER:$PASSWORD $JIRA_URL/jira/rest/atm/1.0/automation/testcases?tql="testCase.projectKey='$PROJECT_KEY'" --output $BUILD_DIR/$TARGET_PATH/$ZIP_FILE

echo "Unzipping feature files"
unzip $BUILD_DIR/$TARGET_PATH/$ZIP_FILE -d $BUILD_DIR/$TARGET_PATH
echo "Finished"


Send Test Results from Bamboo to TM4J

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_FILEZIP_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.

Windows/Cucumber: Publish Test Results to TM4J
set USER=%BAMBOO_jira_user%
set PASSWORD=%BAMBOO_jira_password%
set BUILD_DIR=${bamboo.build.working.directory}
set FILE_PATH="target/cucumber/*.json"
set ZIP_FILE="tm4j_result.zip"
set AUTO_CREATE_TEST_CASES="true"


set PROJECT_KEY="WEB"
set JIRA_URL="http://localhost:2990"

echo "Removing old zip files"
rm -f %BUILD_DIR%/%ZIP_FILE%

echo "Creating new zip file"
7z a %BUILD_DIR%/%ZIP_FILE% %BUILD_DIR%/%FILE_PATH%

echo "Sending zip file to TM4J"
curl --basic --user %USER%:%PASSWORD% -F "file=@%BUILD_DIR%/%ZIP_FILE%;type=application/x-zip-compressed" %JIRA_URL%/jira/rest/atm/1.0/automation/execution/cucumber/%PROJECT_KEY%?=autoCreateTestCases=%AUTO_CREATE_TEST_CASES% -v

echo "Finished"
Windows/JUnit: Publish Test Results to TM4J
set USER=%BAMBOO_jira_user%
set PASSWORD=%BAMBOO_jira_password%
set BUILD_DIR=${bamboo.build.working.directory}
set ZIP_FILE="tm4j_result.zip"
set AUTO_CREATE_TEST_CASES="true"


set PROJECT_KEY="WEB"
set JIRA_URL="http://localhost:2990"

echo "Removing old zip files"
rm -f %BUILD_DIR%/%ZIP_FILE%

echo "Creating new zip file"
7z a %BUILD_DIR%/%ZIP_FILE% %BUILD_DIR%/tm4j_result.json

echo "Sending zip file to TM4J"
curl --basic --user %USER%:%PASSWORD% -F "file=@%BUILD_DIR%/%ZIP_FILE%;type=application/x-zip-compressed" %JIRA_URL%/jira/rest/atm/1.0/automation/execution/%PROJECT_KEY%?autoCreateTestCases=%AUTO_CREATE_TEST_CASES% -v

echo "Finished"
Linux/Cucumber: Publish Test Results to TM4J
USER=$bamboo_jira_user
PASSWORD=$bamboo_jira_password
BUILD_DIR="${bamboo.build.working.directory}"
PATH_FILE="target/cucumber/*.json"
ZIP_FILE="tm4j_result.zip"
AUTO_CREATE_TEST_CASES="true"

JIRA_URL="http://localhost:2990"
PROJECT_KEY="WEB"

echo "Removing old zip files"
rm -f $BUILD_DIR/$ZIP_FILE

echo "Creating new zip file"
zip $BUILD_DIR/$ZIP_FILE $BUILD_DIR/$PATH_FILE -j

echo "Sending zip file to TM4J"
curl --basic --user $USER:$PASSWORD -F "file=@$BUILD_DIR/$ZIP_FILE;type=application/x-zip-compressed" $JIRA_URL/jira/rest/atm/1.0/automation/execution/cucumber/$PROJECT_KEY?autoCreateTestCases=$AUTO_CREATE_TEST_CASES  -v

echo "Finished"
Linux/JUnit: Publish test results to TM4J
USER=$bamboo_jira_user
PASSWORD=$bamboo_jira_password
BUILD_DIR=${bamboo.build.working.directory}
ZIP_FILE="tm4j_result.zip"
AUTO_CREATE_TEST_CASES="true"

PROJECT_KEY="WEB"
JIRA_URL="http://localhost:2990"

echo "Removing old zip files"
rm -f $BUILD_DIR/$ZIP_FILE

echo "Sending zip file to TM4J"
zip $BUILD_DIR/$ZIP_FILE $BUILD_DIR/tm4j_result.json -j

echo "Sending zip file to TM4J"
curl --basic --user $USER:$PASSWORD -F "file=@$BUILD_DIR/$ZIP_FILE;type=application/x-zip-compressed" $JIRA_URL/jira/rest/atm/1.0/automation/execution/$PROJECT_KEY?autoCreateTestCases=$AUTO_CREATE_TEST_CASES -v

echo "Finished"

Applying Scripts in Bamboo

This task describes how to apply scripts in Bamboo for the TM4J integration.

1. Navigate to your Bamboo project.

2. Select the plan you want to configure.

3. On the Actions menu in the upper-right corner, click Configurations.

4. On the Tasks tab, click Add Task.

5. Search for and select the Script task type.

6. Update the field values in the Script Configuration section, as shown. 
Task descriptions will vary.

For Windows:

For Linux:

7. Paste the script into the Script Body.


8. Drag the script task into the desired position.

To transfer your test-execution results from Bamboo back to TM4J, you need to drag the script into the Final Tasks section.

Adding Test Management for Jira annotations

If you are using Cucumber, setup could not be more simple. Add Test Management for Jira annotations to your Cucumber tests, and use our pre-made script to send the results to Jira. The integration is based on the JSON output files generated by Cucumber, so this output option needs to be configured properly, as follows.

1. Configure the JSON output format for your automated tests on the TestRunner class.
Here we’ve added JUnit and Cucumber output formats:

@RunWith(Cucumber.class)
@CucumberOptions(
        features = "src/test/resources/calculatorFeatures"
        ,glue={"com/adaptavist/tm4j/cucumberExample/stepDefinition"}
        ,plugin = {"junit:target/cucumber/result.xml", "json:target/cucumber/calculator.json"}
)

2. Annotate your automated tests with the @TestCaseKey tag.
The @TestCase(key = "JQA-T1") annotation maps the test method to an existing test case in Test Management for Jira by matching its key. The @TestCase(name = "Sum Two Numbers") annotation adds a name to the test case. This maps this test method to an existing test case in Test Management for Jira by matching its name. If the test case doesn’t exist in Test Management for Jira, then a new one can be automatically created using this name when the results are uploaded.

Scenarios can be mapped to test cases in Test Management for Jira by using the test-case key or name as a scenario tag. For example:

@TestCaseKey=ABC-T123.

To Annotate a Cucumber Test

Feature: Calculator

  @TestCaseKey=ABC-T123
  Scenario: Add a number
    Given a calculator I just turned on
    And I add 4 and 4
    Then the result is 8

To Annotate a JUnit Test

public class CalculatorSumTest {

    @Test
    @TestCase(key = "JQA-T1")
    public void sumTwoNumbersAndPass() {
        Calculator calculator = new Calculator();
        assertEquals(5, calculator.sum(3, 2));
    }

    @Test
    @TestCase(key = "JQA-T2")
    public void sumTwoNumbersAndFail() {
        Calculator calculator = new Calculator();
        assertNotEquals(2, calculator.sum(1, 2));
    }

    @Test
    public void notMappedToTestCaseAndPass() {
        Calculator calculator = new Calculator();
        assertEquals(3, calculator.sum(1, 2));
    }

    @Test
    @TestCase(name = "Mapped to a Test Case Name and Pass")
    public void mappedToATestCaseNameAndPass() {
        Calculator calculator = new Calculator();
        assertEquals(4, calculator.sum(2, 2));
    }

}

Now you can run the tests with Maven test, and the Test Management for Jira test execution results file will generate in the same execution folder.


  • No labels