Build #2,184

Build: #2184 was successful Changes by Simon Basle

Build result summary

Details

Completed
Duration
8 minutes
Labels
None
Agent
bamboo-11.af.pivotal.io
Revisions
reactor-core
6f0909cd9cd85289e2e7a03b399c67b459bc1844 6f0909cd9cd85289e2e7a03b399c67b459bc1844
reactor-addons
e92144687fd2bf6319147be33d65f6b53c8958d3 e92144687fd2bf6319147be33d65f6b53c8958d3
Total tests
4738
Successful since
#2174 ()

Code commits

reactor-core
Author Commit Message Commit date
Simon Basle Simon Basle 6f0909cd9cd85289e2e7a03b399c67b459bc1844 6f0909cd9cd85289e2e7a03b399c67b459bc1844 fix #1077 Allow naming of a whole StepVerifier scenario through options
This commit allows a user to name a given `StepVerifier` by providing
a `StepVerifierOptions` that has a `scenarioName(String)` set.

The scenario name will appear in all StepVerifier-produced exceptions
as a prefix wrapped in square brackets, followed by a single space.

Methods of StepVerifier that execute user code which can throw 3rd party
Exceptions will continue propagating these as-is, without the scenario
name prefix (eg. assertNext).

Additionally, the formatting of error messages has been externalized in
a package-protected ErrorFormatter utility class, centralizing the
assembly of error messages (and the prefixing with the scenario name).