diff options
| author | Casper Beyer <caspervonb@pm.me> | 2020-09-15 09:23:20 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-09-14 21:23:20 -0400 |
| commit | 9b8f1d9be880a1f550de7ef7e339c3c58b6bb7ca (patch) | |
| tree | 179e513fb63a91dce2b24f0ee471e7061993ec7f | |
| parent | 70f070706d4de048e1430eebcc0d8de3b469a5bc (diff) | |
docs(testing): describe coverage blackboxing rules (#7483)
| -rw-r--r-- | docs/testing.md | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/docs/testing.md b/docs/testing.md index db81ee341..ca74938e3 100644 --- a/docs/testing.md +++ b/docs/testing.md @@ -209,8 +209,11 @@ deno test --failfast Deno will automatically determine test coverage for your code if you specify the `--coverage` flag when starting `deno test`. Coverage is determined on a line by -line basis, and is acquired directly from the JavaScript runtime (V8). Because -of this, this coverage is very accurate. +line basis for modules that share the parent directory with at-least one test +module that is being executed. + +This coverage information is acquired directly from the JavaScript runtime (V8). +Because of this, the coverage reports are very accurate. When all tests are done running a summary of coverage per file is printed to stdout. In the future there will be support for `lcov` output too. |