deno/tests/testdata/coverage/no_tests_included/foo.test.ts

import { addNumbers } from "./foo.ts";
import { assertEquals } from "../../../../test_util/std/assert/mod.ts";

Deno.test("addNumbers works", () => {
  assertEquals(addNumbers(1, 2), 3);
});
fix(test/coverage): exclude test files (#18748) Fixes: #18454 2023-04-19 23:30:52 +02:00			`import { addNumbers } from "./foo.ts";`
chore: move cli/tests/ -> tests/ (#22369) 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. 2024-02-10 13:22:13 -07:00			`import { assertEquals } from "../../../../test_util/std/assert/mod.ts";`
fix(test/coverage): exclude test files (#18748) Fixes: #18454 2023-04-19 23:30:52 +02:00
			`Deno.test("addNumbers works", () => {`
			`assertEquals(addNumbers(1, 2), 3);`
			`});`