Cucumber integration

RTM supports the direct import of Cucumber JSON reports, allowing you to synchronize your BDD test results with your requirements and test cases.

Test Case identification

For the Cucumber framework, Test Cases linked to imported test results will have a summary consisting of the feature name and scenario name separated by a dot.

Feature: Calculator

  Scenario: Sum Function
    Given I have a calculator
    When I add 5 and 7
    Then the result should be 12

In this example, the generated Test Case summary will be Calculator.Sum Function.

Steps mapping

Each imported scenario creates a Test Case Execution. Every scenario step is mapped to a separate Test Case Execution step, with Cucumber keywords displayed in bold.

The final status for both the Test Case Execution (TCE) and the overall Test Execution (TE) is determined by the “weakest link” principle, ensuring that a single failure is never overlooked in the final report.

Determining TCE status (from steps):

• Failed — if at least one step has a failed status.
• Opening — if no steps are failed, but at least one step is pending.
• Pass — only if all steps within the scenario are passed.
• Default — in all other cases (e.g., some steps are skipped or undefined).

Determining TE status (from TCEs):

• Failed — if at least one TCE (scenario) in the report has a failed status.
• Opening — if no TCEs are failed, but at least one TCE is pending.
• Pass — only if all TCEs in the entire import are passed.
• Default — in all other cases.

Status mapping

Each imported step has its status mapped based on Execution Result Mapping:

Error log

Error messages present on steps are attached as evidence to Test Case Execution steps in a file errors.txt.