Serenity JSON format¶
Download example file (right-click "Save link as..." to download): example_serenity_report.json
nameStored as container title.
descriptionStored as container description, the userStory narrative attribute is used if the description attribute isn't available.
testStepsWe iterate through each test step and their children, the children are defined as the results and each test step as a container.
userStoryThe userStory type and narrative attribute is used for our containers. The classification can be set initially by the type and the description can be set by the narrative attribute.
titleStored as the container title if the name isn't available.
durationignored, counted using child elements that are read as results.
driverSets the report's OS attribute.
A test step will be read as a container with multiple children. In serenity these children generally contain the results which will be processed by calliope.
description: Used to specify the description of the container, initially this is set by the user story narrative attribute.
duration: ignored, the children are used to calculate the duration.
childrenWe iterate through these children to retrieve the results, we do check whether these children contain children before we process all the results.
Steps are rewritten as results
description: Used as result title.
durationUsed to set the estimated duration of the result.
result: Used to determine the status of the result.
- success = passed
- error = failed
- skipped = skipped
- pending = unknown
- undefined = unknown
Linking your scenario's to JIRA¶
This functionality is not there yet, but it is in the pipeline!
By adding a tag to your scenario saying:
@jira_issue_PROJ-201 it will be read as a ticket PROJ-201 to be linked to your scenario.
You can set up your profile to be linked to a JIRA account.