TestOps logo
Try TestOps

Test results upload from Bitbucket

You need to use allurectl to upload the test results of you tests from the Bitbucket CI. In this article we provide basic templates ensuring the expected work with Allure TestOps.

For proper functioning with Bitbucket pipeline reruns on the Allure TestOps side, it is necessary to use allurectl version 2.15.3.

This chapter covers the following:

  1. Authentication of Bitbucket pipeline in Allure TestOps to upload the test results.
  2. Simple (very very simple) pipeline configuration to allow the understanding of the workflows involving allurectl.

Authentication token

For a user on Allure TestOps side you need to create API token.

This API token will be used by allurectl for authentication on Allure TestOps server.

Steps

  1. Log in to Allure TestOps with dedicated account you are going to use to upload test results. That could be your profile as well.

  2. Click on your avatar and go to Your profile.

  3. In the section API tokens click a green button that says Create.

  4. Name your API token and click Submit. Always give meaningful names to all the configuration parameters.

    Allure will randomly generate the token and show you in modal window.

  5. Copy the token and save it in a safe place as it cannot be retrieved by Allure TestOps means.

Test results upload from Bitbucket

Preconditions

You need to read end-to-end the manual for allurectl. In vast majority of the use cases you need watch routine to be used.

We recommend using the environment variables instead of the command line switches to configure allurectl, this approach allows having clearer command line.

Variables needed for allurectl

As per the description of allurectl these are the parameters to be specified:

  • ALLURE_ENDPOINT - mandatory
    • defines the URL of Allure TestOps server, e.g. https://demo.testops.cloud
  • ALLURE_TOKEN - mandatory
    • the API token used for the authentication
  • ALLURE_PROJECT_ID - mandatory
    • the system ID of a project where you are going to upload test results
  • ALLURE_LAUNCH_NAME - mandatory
    • template for the launch name
  • ALLURE_RESULTS - mandatory
    • folder where allurectl should look for the test results
  • ALLURE_LAUNCH_TAGS - optional
    • useful tags to be assigned to a created launch

In the next sections we'll explain where these are could be used.

ALLURE_ENDPOINT in the workspace vars

This is an option, not mandatory placement of this very variable. You can define this variable in the pipeline description as well.

Usually, you have just one instance of Allure TestOps. This means the variable ALLURE_ENDPOINT could be defined on a higher level of Bitbucket entities: for example, in the workspace settings. To open them, use similar path and change {ORGNAME} to the name of your organisation: https://bitbucket.org/{ORGNAME}/workspace/settings/addon/admin/pipelines/account-variables.

Add the variable ALLURE_ENDPOINT and its value to your Bitbucket settings.

The ALLURE_ENDPOINT variable can be set on the Bitbucket's workspace level.

You can also use this variable alongside with the others in a pipeline (explained below).

Simple pipeline

The pipeline logic is described in bitbucket-pipelines.yml file by default. We have no target to teach on how the Bitbucket pipelines need to be organised. We use a simplest possible scenario with custom pipeline.

Pipeline example

image: gradle:8.10-jdk21

pipelines:
  custom:
    test:
      - variables:
          - name: ALLURE_LAUNCH_NAME
            default: ""
          - name: ALLURE_LAUNCH_TAGS
            default: "bitbucket, junit5"

      - step:
          name: Run tests
          script:
            - printenv
            - wget https://github.com/allure-framework/allurectl/releases/latest/download/allurectl_linux_amd64 -O ./allurectl
            - chmod +x ./allurectl
            - ALLURE_LAUNCH_NAME="${BITBUCKET_REPO_FULL_NAME} - $BITBUCKET_BUILD_NUMBER"
            - ./allurectl watch -- gradle --no-daemon clean test
Comments

This part is mandatory for the integration with Allure TestOps as these need to be present in the whole pipeline context and we need to be able to redefine the values of these variables in the runtime of the pipeline.

  custom:
    test:
      - variables:

All the variables from the example need to be added to this very part.

  • ALLURE_LAUNCH_NAME
  • ALLURE_LAUNCH_TAGS

Configure pipeline - Add variables

In previous sections we said, there are variables used by allurectl to send test results to Allure TestOps server.

  • ALLURE_ENDPOINT
  • ALLURE_TOKEN
  • ALLURE_PROJECT_ID

The variable ALLURE_ENDPOINT can be added either to the workspace variables (see above), or it can be added the same way as the other two – on the pipeline configuration level. This is what we'll do now.

  1. Select Source section
  2. Click on bitbucket-pipelines.yml
  3. Click Edit
  4. Then click Edit again
  5. You will see the Configure tab and Add variables settings you need to expand.

The variables can be set on the Bitbucket's project level.

Add the following variables to the section you just opened

  • ALLURE_ENDPOINT
    • not secured
  • ALLURE_TOKEN
    • secured
  • ALLURE_PROJECT_ID
    • not secured
  • ALLURE_RESULTS
    • not secured

We did not mention ALLURE_RESULTS before, but this is a mandatory variable which needs to be visible globally and it won't be changed during the run-time, so it's better to add it here.

After the variables are added, close the window and now you can run your pipeline.

Collecting the information about tests environment

Why?

It is quite a rare situation when tests run without any parameters which define different conditions to run the tests. These conditions could be for instance:

  • different hosts to run the tests on, e.g. QA server, staging server etc.
  • different browsers to run the tests on for web UI tests.
  • VCS branch to test changes before they appear in master branch.

When Allure TestOps collects this information, it will allow you starting the build jobs with the environment of your choice right from its UI.

How?

Add environment variables to a pipeline on Bitbucket side

Env variables can be added to this section where we added vars needed for allurectl:

  custom:
    test:
        - variables:

Let's add the information on the product version under test and the browser the tests use.

  • PRODUCT_VERSION
  • TESTS_BROWSER

Update the pipeline like this

    test:
      - variables:
          - name: ALLURE_LAUNCH_NAME
            default: ""
          - name: ALLURE_LAUNCH_TAGS
            default: "bitbucket, junit5"
          - name: PRODUCT_VERSION
            default: "1.23"
          - name: TESTS_BROWSER
            default: "chrome"

The run pipeline command now will have the following modal dialogue

Environment variables are set via a field in the pipeline settings.

Please ensure the ALLURE_LAUNCH_NAME variable is not left empty. Use code like the following in your pipeline to fill the variable value, which will then pass this information to the Allure TestOps UI:

- ALLURE_LAUNCH_NAME="${BITBUCKET_REPO_FULL_NAME} - $BITBUCKET_BUILD_NUMBER"

Setting up Allure TestOps to process environment variables from Bitbucket

allurectl sends whole set of environment variables from a pipeline to Allure TestOps. This data also includes added environment parameters.

Now, let's set up Allure TestOps project settings for this environments information processing.

Mapping environment variables is configured in the project settings.

  1. Proceed to the project settings

  2. Go to the Environment section

  3. For each variable:

    1. Click Create
    2. Add env variable name to Mapping key
    3. Select global environment variable from the list (these are managed by Allure TestOps administrators)
    4. And Submit

  4. Run the build job from Bitbucket's UI again.

    When the launch appears in the Launches list in Allure TestOps, the variables should be displayed.

Trigger pipelines from Allure TestOps

To trigger pipelines on a CI system (this relates to any CI system in general) you need to have a specific integration added on a) global level b) on the current project level. Then this integration will be used in a Job settings.

This section covers

  1. Integration recap.
  2. Job settings.

The process of the configuration of the integrations with external systems is described here.

Integration recap

  1. Create (get/generate/you name it) the secrets (credentials) on an external system to use their API.
  2. Add the required integration on Allure TestOps global level (you need to be an administrator or have an administrator nearby).
  3. Add the required integration on the project level and provide credentials (secrets) you got on the step 1.

Global level

You need to have ROLE_ADMIN authority to configure Allure TestOps instance on the global level.

  1. Go to User menu > Administration > Integrations
  2. In the upper-right corner click Add integration
  3. Search for Bitbucket
  4. Click on the Bitbucket banner
  5. Provide the name of the integration
    • URL of Bitbucket without http(s):// might be a good idea for the name
  6. Provide Bitbucket's URL to Endpoint field
    • that'll be https://bitbucket.org
  7. Finalise by clicking Add integration.

On the next screen, you can test the connection (good idea!), update the parameters, or even delete the integration (which is bizarre considering you just added it).

Project level

On the level of a project you need to add the created integration to the project you work in, and provide the credentials (secrets) to authorize Allure TestOps to trigger the pipelines.

Bitbucket credentials

To integrate with Bitbucket we need a) user name b) Application password.

You can either use your account, or alternatively you can create a new service account (up to you).

  1. Go to the account configuration https://bitbucket.org/account/settings/
  2. Copy your username (under Bitbucket profile settings)
  3. Go to App passwords settings https://bitbucket.org/account/settings/app-passwords/
  4. Click Create app password
  5. Name the App password
  6. Provide the required permissions
    1. Account read (needed to test the connection)
    2. Issues > Write (if you are going to link the issues Bitbucket to Allure TestOps entities)
    3. Pipeline > Edit variables (to allow setting the values for the variables)
    4. Repositories > Read (to read pipeline file).
  7. Create the App password
  8. Copy the created password
Setup the integration in your Allure TestOps project

You need to be a project owner to configure these settings.

  1. Go to the project's settings.
  2. Go to the Integration section
  3. Locate the Bitbucket integration you want to add.
  4. Click Add integration.
  5. In the modal window enter the credentials – the username and App password we generated on the previous step.
  6. Test the connection
  7. Finalise the Integration settings by clicking on Add integration.

Now, we are ready to configure the Job.

Allure TestOps job settings

Job in Allure TestOps is an entity linked to a CI pipeline. The process of the test results upload is a job-run. All the parameters of a job-run are managed by Allure TestOps and CI plug-in (allurectl).

Pipeline has parameters (passed as env variables) which can be used to trigger a pipeline from Allure TestOps side. To do so, you need to finalise the settings for a Job and create an integration allowing you to trigger the jobs in a CI system.

To be able triggering the associated pipelines, you need to have the configured build server (just done on the previous step).

Also,

To start using a Job for creating Launches and triggering CI pipelines form Allure TestOps UI, you need to configure such a Job:

Multiple environment variables can be specified in the dialog.

  1. Select correct CI server configured on Project level with correct access rights provided in CI.
  2. Mark the Job as available for running tests on it.
  3. Link the ENV variables received from the job to the global environment variables.
  4. Submit the changes.

As you can see, there are 2 special variables:

  • Branch
  • CustomName

Branch on the left needs to be linked to same Branch on the right (Global env variable). In the middle you have the default branch value to run on.

CustomName does not need any matching variable on the right, but requires a default value to be set. This value is your custom pipeline name from bitbucket-pipelines.yml

Trigger a pipeline

Triggering of a pipeline (that'll create a launch in Allure TestOPs) can be done in the following sections of Allure TestOps:

  • List of the test cases – select and use bulk operation Run.
  • List of test results – select and use bulk operation ReRun.
  • Test plans – Click Run button of a test plan.
  • Jobs – Click Run button of a test Job.

All the said actions will result in the modal window with the parameters of a launch Allure TestOps creates for such actions.

Trigger a pipeline on an alternative environment

Alternative means, you want to use the parameters which differ from the ones used in a pipeline by default.

In the job editing dialog in Allure TestOps, click Add environment

Set the required values for the Environment variables you need to alter, and click Save environment.

You can add several sets of the environments, in this case Allure TestOps will create several pipeline executions with different parameters' set and all of them will upload the test results in the same launch.

Complete pipeline example

Here is a very simple Bitbucket pipeline file example providing the general idea of the requirements for the working with Allure TestOps.

# bitbucket-pipelines.yml
image: python:3.8

pipelines:
  custom: 
    pytest python tests:
      - variables:
        - name: ALLURE_LAUNCH_NAME
          default: ""
        - name: ALLURE_LAUNCH_TAGS
          default: "bitbucket, pytest"
        - name: ALLURE_RESULTS
          default: "allure-results"
        - name: TESTS_ENDPOINT
          default: "https://demo.testops.cloud"
        - name: TESTS_BROWSER
          default: "firefox"
        - name: ALLURE_PROJECT_ID
          default: "830"
        - name: ALLURE_ENDPOINT
          default: "https://testing.testops.cloud"

      - step:
          name: pytest tests
          script:
            - /usr/local/bin/python -m pip install --upgrade pip
            - pip install pytest allure-pytest
            - ALLURE_LAUNCH_NAME="${BITBUCKET_REPO_FULL_NAME} - $BITBUCKET_BUILD_NUMBER"
            - wget https://github.com/allure-framework/allurectl/releases/download/2.15.6/allurectl_linux_amd64 -O ./allurectl
            - chmod +x ./allurectl
            - ./allurectl watch -- pytest test --alluredir=${ALLURE_RESULTS}

where pytest python tests: is the mandatory custom pipeline name required for triggering the pipeline via API call.

ALLURE_LAUNCH_NAME, ALLURE_LAUNCH_TAGS, ALLURE_RESULTS, ALLURE_PROJECT_ID, and ALLURE_ENDPOINT are the variables required by allurectl to upload the test results to Allure TestOps.

© Qameta Software Inc. All rights reserved.