Executable Specifications

Serenity BDD CLI

should tell its version

Credentials

defaults to "no credentials" if the credentials are not specified

defaults to "no credentials" if the credentials are empty

complains if the credentials string does not follow the <username>:<password> template

GAV

can be described using a string which format

follows group:artifact:version

follows group:artifact:extension:version

follows group:artifact:extension:classifier:version

can be converted to a file name when the identifier

follows group:artifact:version

follows group:artifact:extension:version

follows group:artifact:extension:classifier:version

SerenityBDDReporter

SerenityBDDReporter

captures information about scenario background

captures the description of the scenario

captures the narrative behind the scenario

SerenityBDDReporter

when reporting activities that took place during scenario execution

reports the outcome of a single activity

reports the outcome of a sequence of several activities

reports the outcome of nested activities

order of events

records the events in a correct order

records the order of test steps so that the Serenity BDD reporter can display the reportData in the correct context

artifacts

records the arbitrary JSON data emitted during the interaction

SerenityBDDReporter

captures information about the business rule for single-scene scenarios

captures information about the business rule for scene sequences

SerenityBDDReporter

captures information about a sequence of scenes (2 scenes in a sequence)

determines the result of the sequence based on the worst result of the contributing scenarios

ensures that context and tags are not duplicated despite having multiple scenarios in a sequence

SerenityBDDReporter

produces a SerenityBDDReport that

can be tagged

@manual

is marked as automated (non-manual) by default

can be optionally tagged as manual

@issue

can be tagged with an issue number

@arbitrary-tag

can be tagged with an arbitrary tag

to indicate that a scenario

belongs to a feature

belongs to a capability

belongs to a theme

is executed in the context and

indicates the web browser where the test was executed

indicates the operating system where the test was executed

ensures that the user-specified context takes precedence over browser context

SerenityBDDReporter

generates a SerenityBDDReport Artifact that

is a valid artifact

emits an ArtifactGenerated event that

is separate for each scenario

produces a SerenityBDDReport that

at the scenario level

contains the id of the scenario

contains the name of the scenario

contains the start time of the scenario

contains the duration of the scenario

describes the result of scenario execution that

has finished with success

hasn't been implemented yet

has been ignored

has been skipped

has failed with an assertion error

has been compromised

has failed with a non-assertion error

has been compromised

indicates its execution context

specifies the test runner

specifies the user story covered

does not mention the user story path for non-Cucumber scenarios (as it breaks the Serenity BDD HTML report)

reports information from the cucumber feature file

reports the scenario-level narrative

reports the scenario-level background title

reports the scenario-level background description

attachements

todo

Error handling

generates the report even when the test runner has crashed

errorReportFrom

when representing Errors as Serenity BDD-standard JSON reports

supports native Error

supports Serenity/JS Errors

supports Serenity/JS Errors with root causes

when representing non-Error "throwables" as Serenity BDD-standard JSON reports

supports null

supports undefined

supports objects

supports arrays

supports numbers

supports strings

supports booleans

SerenityBDDReporter