Major Description
As system, Cucumber step output must be imported whenever Cucumber results are imported from a JSON report.
Example of Cucumber JSON report with a step.
[
{
"uri": "features/print_from_step_definition.feature",
"id": "a-print-from-step-definition-feature",
"keyword": "Feature",
"name": "A print from step definition feature",
"line": 1,
"description": "",
"elements": [
{
"id": "a-print-from-step-definition-feature;",
"keyword": "Scenario",
"name": "",
"line": 3,
"description": "",
"type": "scenario",
"steps": [
{
"keyword": "Given ",
"name": "I print from step definition",
"line": 4,
"output": [
"from step definition"
],
"match": {
"location": "features/step_definitions/json_steps.rb:6"
},
"result": {
"status": "passed",
"duration": 1
}
},
{
"keyword": "And ",
"name": "I print from step definition",
"line": 5,
"output": [
"from step definition"
],
"match": {
"location": "features/step_definitions/json_steps.rb:6"
},
"result": {
"status": "passed",
"duration": 1
}
}
]
}
]
}
]
ACs:
- whenever importing Cucumber JSON from UI within a Test Execution, the Cucumber step level "output" must be imported (if available)
- whenever importing Cucumber JSON from REST API (standard or multipart), the Cucumber step level "output" must be imported (if available)
- multiple elements of the "output" array element should be concatenated using "new lines"/line breaks in the execution detail page
Reference: