[reactor-test] Add StepVerifier option to use ConditionalSubscriber #3035
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit adds a new feature to StepVerifier that enforces the use
of a ConditionalSubscriber as the verifier's Subscriber.
It is activated by calling
enableConditionalSupport
at anyStep
(similar to the
as
naming method). Note that the reason the feature isadded to the
Step
API is that it is the only part that is typed with<T>
(which is desirable for thePredicate
to be typed).This feature only guarantees that the StepVerifier will use a subscriber
that implements ConditionalSubscriber when it subscribes to the source.
Note that this doesn't guarantee the Publisher under test is itself
going to produce ConditionalSubscribers, and even if it does, this
doesn't guarantee that at runtime the
tryOnNext
path will be used.All of this depends on the source and the publisher chain under test.