Fixes

Author: dkhalanskyjb

kotlinx-coroutines-test/MIGRATION.md

@@ -17,7 +17,7 @@ was called.
 
 We currently don't provide a replacement for this.
 However, `runTest` follows structured concurrency better than `runBlockingTest` did, so exceptions from child coroutines
-are propagated structurally in more cases than before, which makes uncaught exception handlers less useful.
+are propagated structurally, which makes uncaught exception handlers less useful.
 
 If you have a use case for this, please tell us about it at the issue tracker.
 Meanwhile, it should be possible to use a custom exception captor, which should only implement
@@ -78,12 +78,13 @@ It is already illegal to use a `TestCoroutineScope` without performing `cleanupT
   An example is shown below.
 
 ```kotlin
+val exceptions = mutableListOf<Throwable>()
+val customCaptor = CoroutineExceptionHandler { ctx, throwable ->
+    exceptions.add(throwable) // add proper synchronization if the test is multithreaded
+}
+
 @Test
 fun testFoo() = runTest {
-    val exceptions = mutableListOf<Throwable>()
-    val customCaptor = CoroutineExceptionHandler { ctx, throwable ->
-      exceptions.add(throwable) // add proper synchronization if the test is multithreaded
-    }
     launch(customCaptor) {
         // ...
     }

kotlinx-coroutines-test/README.md

@@ -111,8 +111,6 @@ on Kotlin/JS. The main differences are the following:
   guide the execution, advancing the virtual time by a duration, draining the queue of the awaiting tasks, or running
   the tasks scheduled at the present moment.
 * **Handling uncaught exceptions** spawned in the child coroutines by throwing them at the end of the test.
-* **Detecting unfinished jobs**, that is, tasks that are still pending by the end of the test, in order to prevent
-  coroutine leaks.
 * **Waiting for asynchronous callbacks**.
   Sometimes, especially when working with third-party code, it's impossible to mock all the dispatchers in use.
   [runTest] will handle the situations where some code runs in dispatchers not integrated with the test module.
@@ -318,11 +316,6 @@ fun testEagerlyEnteringSomeChildCoroutines() = runTest(UnconfinedTestDispatcher(
 }
 ```
 
-## Detecting unfinished jobs
-
-The test framework ensures that coroutines are not leaked.
-To this end, the coroutines that aren't finished by the end of the test are reported.
-
 ### Using `withTimeout` inside `runTest`
 
 Timeouts are also susceptible to time control, so the code below will immediately finish.