From dc6673124ed5cc8a532abe6511484d8d8ceebbf9 Mon Sep 17 00:00:00 2001 From: Jay Phelps Date: Wed, 9 May 2018 08:52:27 -0400 Subject: [PATCH] docs(marble-testing.md): fix #known-issues link (#3670) --- doc/marble-testing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/marble-testing.md b/doc/marble-testing.md index d2a52a5b15..0d854db93a 100644 --- a/doc/marble-testing.md +++ b/doc/marble-testing.md @@ -4,7 +4,7 @@ We can test our _asynchronous_ RxJS code _synchronously_ and deterministically by virtualizing time using the TestScheduler. ASCII **marble diagrams** provide a visual way for us to represent the behavior of an Observable. We can use them to assert that a particular Observable behaves as expected, as well as to create [hot and cold Observables](https://medium.com/@benlesh/hot-vs-cold-observables-f8094ed53339) we can use as mocks. -> At this time the TestScheduler can only be used to test code that uses timers, like delay/debounceTime/etc (i.e. it uses AsyncScheduler with delays > 1). If the code consumes a Promise or does scheduling with AsapScheduler/AnimationFrameScheduler/etc it cannot be reliably tested with TestScheduler, but instead should be tested more traditionally. See the [Known Issues](#Known-Issues) section for more details. +> At this time the TestScheduler can only be used to test code that uses timers, like delay/debounceTime/etc (i.e. it uses AsyncScheduler with delays > 1). If the code consumes a Promise or does scheduling with AsapScheduler/AnimationFrameScheduler/etc it cannot be reliably tested with TestScheduler, but instead should be tested more traditionally. See the [Known Issues](#known-issues) section for more details. ```ts const testScheduler = new TestScheduler((actual, expected) => {