Docs
Cucumber BDD

Integrating Cucumber BDD with TestRail

Cucumber BDD framework (opens in a new tab) is a popular functional testing framework which is used by many software development and QA teams. Railflow (opens in a new tab) integration solutions helps users integrate Cucumber BDD tests with TestRail with basic configurations and without any hassle. Railflow consumes the native Cucumber BDD results report, extracts all the results information, and uploads it to TestRail using the TestRail REST API.

Railflow for Cucumber BDD provides the following capabilities

  • Test Mapping: Map Cucumber scenarios to existing tests in TestRail
  • Auto Extraction: Automatically process Cucumber reports
  • Custom Fields: Support for TestRail custom fields.
  • TestRail Entities: Update / Create Test Plans, Runs, Milestone, Tests, Results
  • Smart Failure Assignment: Auto assign test failures to TestRail user
  • CI Application: Support for Jenkins, TeamCity, Gitlab, Github, etc.

Sample Project

To demonstrate this integration, we have created a sample project using Cucumber BDD using Selenium (opens in a new tab)

Feature File

Lets say we have a feature file containing two simple scenarios

cucumber
Feature: Pizza tests
  Some tests for pizza search
 
  Background:
    Given user navigates to https://google.com
 
  Scenario: There are results for pizza
    When the user enters "pizza" and hits Enter
    Then number of results more than zero
 
  Scenario: There are no bad pizzas
    When the user enters "bad pizza" and hits Enter
    Then no results are shown

Test Mapping

Many teams first define tests in TestRail and then write Cucumber BDD tests. Railflow provies a way to map the Cucumber tests to the existing TestRail tests by using Cucumber tag @testrail.id=C123 in the feature file where C123 is the ID of the existing test case in TestRail. This tag and value is automatically extracted from the cucumber reports by Railflow CLI and used to update the test results in TestRail.

Mapping cucumber scenario into TestRail test case
Feature: Pizza tests
  Some tests for pizza search
 
  Background:
    Given user navigates to https://google.com
 
  @testrail.id=C1234
  Scenario: There are results for pizza
    When the user enters "pizza" and hits Enter
    Then number of results more than zero
 
  @testrail.id=C928
  Scenario: There are no bad pizzas
    When the user enters "bad pizza" and hits Enter
    Then no results are shown

Cucumber Test Runner

In order to run JUnit tests together with Cucumber we need to configure Cucumber Test Runner. To do this, just add io.railflow.demo.cucumber.TestRunner class. This code also generates the JSON report in target/test-report.json. This report will be consumed by TestRail CLI or CI Plugins.

cucumber example
package io.railflow.demo.cucumber;
 
import org.junit.runner.RunWith;
 
import io.cucumber.junit.Cucumber;
import io.cucumber.junit.CucumberOptions;
 
 
@RunWith(Cucumber.class)
@CucumberOptions(plugin = { "json:target/test-report.json" })
public class TestRunner {
 
}
maven test
mvn clean test

Railflow CLI

Once the Cucumber test-report.json is generated, it can be uploaded to TestRail using the Railflow CLI (opens in a new tab) or CI plugins (opens in a new tab).

Railflow CLI command for Cucumber
npx railflow -k <license key> -url <testrail address> -u <username> -p <password> -pr <project name> -path <suite name>/<section name>/<subsection name> -f cucumber -r test-report.json -sm <search mode> -tp [test plan name] -mp [milestone path]

railflow cli

railflow cli

railflow cli

railflow cli

CLI Reference

Railflow CLI will automatically create tests, runs, plans, milestones, etc. if they do not exist.

Environment Variables: To avoid exposing sensitive information like TestRail URL, License, username, and password in CLI arguments, users can set the following environment variables: RAILFLOW_LICENSE, RAILFLOW_TR_URL, RAILFLOW_TR_USER, RAILFLOW_TR_PASSWORD. Railflow CLI will always check these environment variables at run time.

⚠️

Use double quotes for argument values with spaces. Example: --project "demo project"

KeyRequiredDescriptionExample
-v, --versionNoOutputs Railflow version number-v
-k, --key-k or -l(online activation) License key. Can be set with RAILFLOW_LICENSE environment variable-k XXXXX-XXXXX-XXXXX-XXXXX
-l, --license-file-k or -l(offline activation) File path or remote url license file-l /files/ActivationFile.skm
-url, --urlYesTestRail instance URL. Can be set with RAILFLOW_TR_URL environment variable-url https://example.testrail.io (opens in a new tab)
-u, --usernameYesTestRail username. Can be set with RAILFLOW_TR_USER environment variable-u test-username
-p, --passwordYesTestRail password or API Key. Can be set with RAILFLOW_TR_PASSWORD environment variable-p XtpHXiPLEODyhF
-pr, --projectYesTestRail project name-pr "example project"
-path, --test-pathYesTestRail test cases path-path "Section1/subsection2/ShoppingCart
-f, --formatYesReport format: JUnit, JUnit-Steps, TestNg, TestNg-Steps, Cucumber, NUnit, NUnit-SpecFlow, Allure, Robot, TRX, xUnit, PyTest-Railflow, Playwright (case insensitive)-f junit
-r, --report-filesYesThe file path(s) to the test report file(s) generated during the build. User can pass multiple values separated with spaces. Ant-style patterns such as **/surefire-reports/*.xml can be used.
E.g. use target/surefire-reports/*.xml to capture all XML files in target/surefire-reports directory.
-r target/surefire-reports/*.xml target/failsafe-reports/*.xml
-sm, --search-modeYesSpecifies the test case lookup algorithm.
name: search for test case matching the name within the entire test suite. If test case found, update the test case. If test case not found, create a new test case within specified -path
path: search for test case matching the name within the specified -path. If test case found, update the test case. If test case not found, create a new test case within specified -path
-sm path
-px, --proxyNoHTTP or SOCKS proxy configuration
E.g. socks://username:[email protected]:1080
-px socks://username:[email protected]:1080
-t, --timeoutNoUpload timeout (seconds)-t 10
-tr, --test-runNoTestRail test run name-tr "Chrome Regression Run"
-tp, --test-planNoTestRail test plan Name-tp "Shopping Cart Test Plan"
-mp, --milestone-pathNoTestRail milestone path-mp Milestone1/Milestone2
-cf, --case-fieldsNoTestRail test case custom fields.
The format is [Field label]=[value] pairs, separated with space.
E.g. "Case Field 1=value 1" "Case Field 2=value 2" ...
-cf "Case Field 1=value 1" "Case Field 2=value 2"
-rf, --result-fieldsNoTestRail test result custom fields.
The format is [Field label]=[value] pairs, separated with space.
E.g. "Result Field 1=value 1" "Result Field 2=value 2" ...
-rf "Result Field 1=value 1" "Result Field 2=value 2"
-a, --assignNoSmart Test Failure Assignment. Comma-separated list of TestRail users (email addresses). Railflow will assign failures based on a round robin algorithm.-a [email protected],[email protected]
-af, --assign-fileNoSmart Test Failure Assignment. File path containing list of TestRail users (email addresses).
Note: One user per line
-af /assignees.txt
-cn, --config-namesNoTestRail test plan configuration options.
Configuration format is: [config_group_name]/[config_name].
E.g. "Operating Systems/Linux" "Browsers/Chrome" ...
-cn "Operating Systems/Linux" "Browsers/Chrome"
-cr, --close-runNoIf Railflow should close the corresponding run after uploading test results-cr
-cp, --close-planNoIf Railflow should close the corresponding plan after uploading test results-cp
-dg, --disable-groupingNoIf Railflow should ignore report structure and just upload all tests into a folder which is set by test-path parameter-dg
-tn, --template-nameNoThe name of a template to use in TestRail. If it is not set, 'Test Case (Steps)' or the default one will be used-tn "Test Case (Steps)"
-cst, --case-typeNoThe name of a type for cases-cst other
-csp, --case-priorityNoThe name of a priority for cases-csp medium
-th, --thread-numberNoThe number of concurrent threads for exporting data. Default is 4-th 8
-um, --upload-modeNoUpload mode. Available values are:
0 (default) - create new test cases and do not overwrite existing ones;
1 - create new cases and overwrite existing ones;
2 - do not create new cases and overwrite existing ones;
3 - do not create new cases and do not overwrite existing ones
-um 1
-csf, --case-search-fieldNoThe name of the case field in TestRail which will be using for searching for existing test cases instead of test case title-csf "Custom field"
-ds, --disable-statsNoIf Railflow should disable collecting usage and error logs-ds
-fqtn, --fully-qualified-test-nameNoIf checked, Railflow will use fully qualified test names from the report files for test names in TestRail-fqtn
-us, --untested-statusNoThe name of the status to use in TestRail for untested/skipped tests-us Skipped
-ams, --attachment-max-sizeNoMaximum size of an attachment. Can be set in Gb, Mb, Kb or b. If the unit is not provided considered as Mb.
E.g. 1Gb, 2, 20Kb, 3Mb
-ams 1Gb
-atw, --attachment-type-whitelistNoThe comma-separated list of file extensions which are allowed to upload. E.g. json, .html, .xml-atw "json, .html, .xml"
-atb, --attachment-type-blacklistNoThe comma-separated list of file extensions which are not allowed to upload. E.g. json, .html, .xml-atb "json, .html, .xml"
-nr, --no-runNoDo not create or update Test Run in TestRail-nr
-tfn, --tags-field-nameNoThe name of a test case field which will be holding tags from the report file if any. E.g. Cucumber Tags-tfn "Cucumber Tags"
-h, --helpNoShow the help information-h