forked from ReactiveX/RxJava
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathOperatorTester.java
More file actions
94 lines (80 loc) · 3.35 KB
/
Copy pathOperatorTester.java
File metadata and controls
94 lines (80 loc) · 3.35 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
/**
* Copyright 2013 Netflix, Inc.
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package rx.test;
import java.util.concurrent.TimeUnit;
import rx.Scheduler;
import rx.Subscription;
import rx.util.functions.Action0;
import rx.util.functions.Func2;
/**
* Common utility functions for testing operator implementations.
*/
public class OperatorTester {
/*
* This is purposefully package-only so it does not leak into the public API outside of this package.
*
* This package is implementation details and not part of the Javadocs and thus can change without breaking backwards compatibility.
*
* benjchristensen => I'm procrastinating the decision of where and how these types of classes (see rx.subjects.UnsubscribeTester) should exist.
* If they are only for internal implementations then I don't want them as part of the API.
* If they are truly useful for everyone to use then an "rx.testing" package may make sense.
*/
private OperatorTester() {
}
/**
* Used for mocking of Schedulers since many Scheduler implementations are static/final.
*
* @param underlying
* @return
*/
public static Scheduler forwardingScheduler(Scheduler underlying) {
return new ForwardingScheduler(underlying);
}
public static class ForwardingScheduler extends Scheduler {
private final Scheduler underlying;
public ForwardingScheduler(Scheduler underlying) {
this.underlying = underlying;
}
@Override
public Subscription schedule(Action0 action) {
return underlying.schedule(action);
}
@Override
public <T> Subscription schedule(T state, Func2<? super Scheduler, ? super T, ? extends Subscription> action) {
return underlying.schedule(state, action);
}
@Override
public Subscription schedule(Action0 action, long dueTime, TimeUnit unit) {
return underlying.schedule(action, dueTime, unit);
}
@Override
public <T> Subscription schedule(T state, Func2<? super Scheduler, ? super T, ? extends Subscription> action, long dueTime, TimeUnit unit) {
return underlying.schedule(state, action, dueTime, unit);
}
@Override
public Subscription schedulePeriodically(Action0 action, long initialDelay, long period, TimeUnit unit) {
return underlying.schedulePeriodically(action, initialDelay, period, unit);
}
@Override
public <T> Subscription schedulePeriodically(T state, Func2<? super Scheduler, ? super T, ? extends Subscription> action, long initialDelay, long period, TimeUnit unit) {
return underlying.schedulePeriodically(state, action, initialDelay, period, unit);
}
@Override
public long now() {
return underlying.now();
}
}
}