deno.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2024-05-28	fix(coverage): skip generating coverage json for http(s) scripts (#24008)	Yoshiya Hinosawa
	closes #21784
2024-05-28	fix(coverage): handle ignore patterns (#23974)	Yoshiya Hinosawa
	closes #23972
2024-05-26	fix(coverage): add tooltip to line count in html report (#23971)	Yoshiya Hinosawa
	closes #21582
2024-05-21	fix(cli/coverage): invalid line id in html reporter (#23908)	Simon Lecoq

2024-05-13	fix(cli): panic with `deno coverage` (#23353)	Evan
	This PR directly addresses the issue raised in #23282 where Deno panics if `deno coverage` is called with `--include` regex that returns no matches. I've opted not to change the return value of `collect_summary` for simplicity and return an empty `HashMap` instead
2024-05-08	chore: cleanup some coverage tests (#23738)	David Sherret

2024-03-15	chore: move more tests away from itest (#22909)	David Sherret
	Part of #22907
2024-02-12	chore: continue tests/ re-org (#22396)	Matt Mastracci
	Split `node_compat_tests` into its own top-level test so its stdout doesn't stomp on the remainder of the tests.
2024-02-10	chore: move cli/tests/ -> tests/ (#22369)	Matt Mastracci
	This looks like a massive PR, but it's only a move from cli/tests -> tests, and updates of relative paths for files. This is the first step towards aggregate all of the integration test files under tests/, which will lead to a set of integration tests that can run without the CLI binary being built. While we could leave these tests under `cli`, it would require us to keep a more complex directory structure for the various test runners. In addition, we have a lot of complexity to ignore various test files in the `cli` project itself (cargo publish exclusion rules, autotests = false, etc). And finally, the `tests/` folder will eventually house the `test_ffi`, `test_napi` and other testing code, reducing the size of the root repo directory. For easier review, the extremely large and noisy "move" is in the first commit (with no changes -- just a move), while the remainder of the changes to actual files is in the second commit.