Deno will collect test coverage into a directory for your code if you specify
--coverage flag when starting
This can then be further processed from the internal format into well known
formats by the
deno coverage tool.
⚠️ To ensure consistent coverage results, make sure to process coverage data immediately after running tests. Otherwise source code and collected coverage data might get out of sync and unexpectedly show uncovered lines.
# Go into your project's working directory git clone https://github.com/oakserver/oak && cd oak # Collect your coverage profile with deno test --coverage=<output_directory> deno test --coverage=cov_profile # From this you can get a pretty printed diff of uncovered lines deno coverage cov_profile # Or generate an lcov report deno coverage cov_profile --lcov --output=cov_profile.lcov # Which can then be further processed by tools like genhtml genhtml -o cov_profile/html cov_profile.lcov
deno coverage will exclude any files matching the regular
test\.(ts|tsx|mts|js|mjs|jsx|cjs|cts) and only consider including
specifiers matching the regular expression
^file: - ie. remote files will be
excluded from coverage report.
These filters can be overridden using the
--include flags. A
module specifier must match the include_regular expression and not match the
exclude_ expression for it to be a part of the report.