top of page
  • Writer's pictureNick

AssertThat BDD Jira plugin now with Jenkins plugin integration

Streamlining DevOps: AssertThat's Jenkins Integration for Jira

Integration between AssertThat's BDD, Cucumber & Test Management plugin for Jira and your test automated framework couldn't be easier with our Jenkins plugin

AssertThat have released our plugin for Jenkins the go-to dev-ops tool.

The Jenkins plugin provides integration between AssertThat's BDD & Cucumber plugin for Jira and your Test Automation Framework.

What Does the plugin do?

The plugin provides seamless integration for:

  • Downloading feature files from AssertThat's BDD & Cucumber plugin for Jira into your Test Automation framework before test run

  • Filtering features to download based on mode (automated/manual/both), or/and Jira JQL

  • Uploading cucumber json after the run to AssertThat's BDD & Cucumber plugin for Jira. Enabling you to view your test automated results alongside your user stories in Jira.

1. Installing the plugin

From Jenkins plugin manager, the plugin can be found at:


2. Create credentials

The Jenkins plugin requires the following credentials for authentication:

* Project ID

* AssertThat BDD Access Key

* AssertThat BDD Secret Key

All this information can be found from the AssertThats Integration screen in Jira. Details of how to access the screen are available from AssertThat Integration page.

Screenshot of Jenkins interface showing the 'Add Credentials' screen, highlighting fields for entering AssertThat plugin credentials
Adding Credentials in Jenkins for AssertThat Integration: A Step-by-Step View.

3. Usage in Job

The plugin performs 2 functions:

Download features:

  • Jira project ID (mandatory)

  • Credentials as defined above

  • Feature output folder (optional)

  • JIRA JQL (optional) - JQL filters can be developed using the JIRA's advanced searching functionality e.g. “Sprint = 5”

  • Mode - defines whether to download automated, manual or both types of scenarios from AssertThat.

Image of Jenkins displaying the Download Features Configuration for the AssertThat plugin, showing various settings options
Configuring Download Features in Jenkins for AssertThat: Streamlining BDD in Jira

Upload reports:

  • Jira project id (mandatory)

  • Credentials (mandatory)

  • Json output folder (optional)

  • Json pattern (optional) - can be used to filter json files

  • Run name (optional) - Update this field to overwrite Test Run name when uploaded to AssertThat. Default will be Test run + timestamp

Screenshot depicting the Upload Report configuration in Jenkins for the AssertThat plugin, illustrating the setup for reporting test results.
Setting Up Upload Report in Jenkins: Integrating Test Results with AssertThat.

Usage in pipeline Job


pipeline {

agent any

stages {

stage('Features') {

steps {

//Download feature files

assertthatBddFeatures(credentialsId: '10005-creds', jql: 'project=DEMO', mode: 'automated', outputFolder: 'features', projectId: '10005')



stage('Run tests') {

steps {

//Run tests here






//Upload test results

assertthatBddReport(credentialsId: '10005-creds', jsonReportFolder: 'report', jsonReportIncludePattern: '**/*.json', projectId: '10005', runName: 'Smoke test run')



Free Trial

If you would like a free demo or trial then please click on the button below or get in contact with us at

113 views0 comments

Recent Posts

See All


bottom of page