denoland-deno/cli/tests/testdata/coverage/expected_complex.out

cover [WILDCARD]complex.ts ... 60.000% (24/40)
  46 | export function unused(
  47 |   foo: string,
  48 |   bar: string,
  49 |   baz: string,
  50 | ): Complex {
  51 |   return complex(
  52 |     foo,
  53 |     bar,
  54 |     baz,
  55 |   );
  56 | }
-----|-----
  64 | export function ƒ(): number {
  65 |   return (
  66 |     0
  67 |   );
-----|-----
  71 | console.log("%s", () => 1);
fix(cli): ensure empty lines don't count towards coverage (#11957) 2021-10-06 01:05:18 -04:00			`cover [WILDCARD]complex.ts ... 60.000% (24/40)`
feat: add "deno coverage" subcommand (#8664) This commit adds a new subcommand called "coverage" which can generate code coverage reports to stdout in multiple formats from code coverage profiles collected to disk. Currently this supports outputting a pretty printed diff and the lcov format for interoperability with third-party services and tools. Code coverage is still collected via other subcommands that run and collect code coverage such as "deno test --coverage=<directory>" but that command no longer prints a pretty printed report at the end of a test run with coverage collection enabled. The restrictions on which files that can be reported on has also been relaxed and are fully controllable with the include and exclude regular expression flags on the coverage subcommand. Co-authored-by: Luca Casonato <lucacasonato@yahoo.com> 2021-02-24 09:27:51 -05:00			`46 \| export function unused(`
			`47 \| foo: string,`
			`48 \| bar: string,`
			`49 \| baz: string,`
fix(cli): ensure empty lines don't count towards coverage (#11957) 2021-10-06 01:05:18 -04:00			`50 \| ): Complex {`
feat: add "deno coverage" subcommand (#8664) This commit adds a new subcommand called "coverage" which can generate code coverage reports to stdout in multiple formats from code coverage profiles collected to disk. Currently this supports outputting a pretty printed diff and the lcov format for interoperability with third-party services and tools. Code coverage is still collected via other subcommands that run and collect code coverage such as "deno test --coverage=<directory>" but that command no longer prints a pretty printed report at the end of a test run with coverage collection enabled. The restrictions on which files that can be reported on has also been relaxed and are fully controllable with the include and exclude regular expression flags on the coverage subcommand. Co-authored-by: Luca Casonato <lucacasonato@yahoo.com> 2021-02-24 09:27:51 -05:00			`51 \| return complex(`
			`52 \| foo,`
			`53 \| bar,`
			`54 \| baz,`
			`55 \| );`
			`56 \| }`
			`-----\|-----`
			`64 \| export function ƒ(): number {`
			`65 \| return (`
			`66 \| 0`
			`67 \| );`
fix(coverage): ensure single line functions don't yield false positives (#9717) 2021-03-08 05:51:01 -05:00			`-----\|-----`
			`71 \| console.log("%s", () => 1);`