From 9b8f1d9be880a1f550de7ef7e339c3c58b6bb7ca Mon Sep 17 00:00:00 2001 From: Casper Beyer Date: Tue, 15 Sep 2020 09:23:20 +0800 Subject: [PATCH] docs(testing): describe coverage blackboxing rules (#7483) --- docs/testing.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/testing.md b/docs/testing.md index db81ee3410..ca74938e32 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.