Subscription
actually solves the "unbounded recursion" problem by not allowing the number of
recursive calls to exceed the number returned by this method.Subscription
actually solves the "unbounded recursion" problem by not allowing the number of
recursive calls to exceed the number returned by this method.TestEnvironment#printlnDebug
is true, print debug message to std out.DEFAULT_TIMEOUT_MILLIS
as long and returns the value if present OR its default value.PUBLISHER_REFERENCE_GC_TIMEOUT_MILLIS
as long and returns the value if present,
OR its default value (PublisherVerification.DEFAULT_PUBLISHER_REFERENCE_GC_TIMEOUT_MILLIS
).method
method in stack trace.Subscription
is cancelled.Subscription
is cancelled.Subscription
is cancelled.Publisher
PublisherVerification.maxElementsFromPublisher()
to mark that the given Publisher
,
is not able to signal completion.Publisher
specification rules.true
in order to skip executing tests marked as Stochastic
.true
in order to skip executing tests marked as Stochastic
.n
times.SubscriberBlackboxVerification.BlackboxTestStage.sub()
Subscriber
, providing certain assertions on methods being called on the Subscriber.Subscriber
and Subscription
specification rules, without any modifications to the tested implementation (also known as "Black Box" testing).SubscriberWhiteboxVerification.WhiteboxTestStage
over to the test.SubscriberWhiteboxVerification.WhiteboxTestStage
without performing any additional setup,
like the SubscriberWhiteboxVerification.subscriberTest(SubscriberWhiteboxVerification.TestStageTestRun)
would.Subscriber
and Subscription
specification rules.Subscriber
decorator and should be used in pub.subscriber(...)
calls,
in order to allow intercepting calls on the underlying Subscriber
.TestEnvironment.ManualSubscriberWithSubscriptionSupport
but does not accumulate values signalled via onNext
, thus it can not be used to assert
values signalled to this subscriber.Subscriber
implementation which can be steered by test code and asserted on.TestEnvironment.defaultTimeoutMillis()
and then verifies that no asynchronous errors
were signalled pior to, or during that time (by calling flop()
).verifyNoAsyncErrors
should be used when errors still could be signalled
asynchronously during TestEnvironment.defaultTimeoutMillis()
time.flop()
).id
value.