All Classes and Interfaces

Class
Description
AsyncIterablePublisher is an implementation of Reactive Streams `Publisher` which executes asynchronously, using a provided `Executor` and produces elements from a given `Iterable` in a "unicast" configuration to its `Subscribers`.
 
 
 
 
 
AsyncSubscriber is an implementation of Reactive Streams `Subscriber`, it runs asynchronously (on an Executor), requests one element at a time, and invokes a user-defined method to process each element.
 
 
 
 
 
Bridge between Reactive Streams API and the Java 9 Flow API.
Flow Publisher that wraps a Reactive Streams Publisher.
Wraps a Reactive Streams Processor and forwards methods of the Flow Processor to it.
Wraps a Reactive Streams Subscriber and forwards methods of the Flow Subscriber to it.
Wraps a Reactive Streams Subscription and converts the calls to a Flow Subscription.
Reactive Streams Publisher that wraps a Flow Publisher.
Wraps a Flow Processor and forwards methods of the Reactive Streams Processor to it.
Wraps a Flow Subscriber and forwards methods of the Reactive Streams Subscriber to it.
Wraps a Flow Subscription and converts the calls to a Reactive Streams Subscription.
Provides tests for verifying a Java 9+ Flow.Publisher specification rules.
Provides tests for verifying Flow.Subscriber and Flow.Subscription specification rules, without any modifications to the tested implementation (also known as "Black Box" testing).
Provides whitebox style tests for verifying Flow.Subscriber and Flow.Subscription specification rules.
 
 
 
 
 
 
Copy of scala.control.util.NonFatal in order to not depend on scala-library
 
 
 
A Processor represents a processing stage—which is both a Subscriber and a Publisher and obeys the contracts of both.
A Publisher is a provider of a potentially unbounded number of sequenced elements, publishing them according to the demand received from its Subscriber(s).
Provides tests for verifying Publisher specification rules.
 
Internal TCK use only.
A synchronous implementation of the Publisher that can be subscribed to multiple times and each individual subscription will receive range of monotonically increasing integer values on demand.
A Subscription implementation that holds the current downstream requested amount and responds to the downstream's request() and cancel() calls.
Will receive call to Subscriber.onSubscribe(Subscription) once after passing an instance of Subscriber to Publisher.subscribe(Subscriber).
Provides tests for verifying Subscriber and Subscription specification rules, without any modifications to the tested implementation (also known as "Black Box" testing).
Internal TCK use only.
 
Provides whitebox style tests for verifying Subscriber and Subscription specification rules.
 
This class is intented to be used as Subscriber decorator and should be used in pub.subscriber(...) calls, in order to allow intercepting calls on the underlying Subscriber.
 
Implement this puppet in your Whitebox style tests.
 
 
Internal TCK use only.
A Subscription represents a one-to-one lifecycle of a Subscriber subscribing to a Publisher.
SyncSubscriber is an implementation of Reactive Streams `Subscriber`, it runs synchronously (on the Publisher's thread) and requests one element at a time and invokes a user-defined method to process each element.
 
Similar to TestEnvironment.ManualSubscriberWithSubscriptionSupport but does not accumulate values signalled via onNext, thus it can not be used to assert values signalled to this subscriber.
Like a CountDownLatch, but resettable and with some convenience methods
 
 
 
Subscriber implementation which can be steered by test code and asserted on.
 
 
 
 
Exception used by the TCK to signal failures.
Type which is able to create elements based on a seed id value.