summaryrefslogtreecommitdiff
path: root/cli/tests/testdata/test/uncaught_errors.out
diff options
context:
space:
mode:
authorMatt Mastracci <matthew@mastracci.com>2024-02-10 13:22:13 -0700
committerGitHub <noreply@github.com>2024-02-10 20:22:13 +0000
commitf5e46c9bf2f50d66a953fa133161fc829cecff06 (patch)
tree8faf2f5831c1c7b11d842cd9908d141082c869a5 /cli/tests/testdata/test/uncaught_errors.out
parentd2477f780630a812bfd65e3987b70c0d309385bb (diff)
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.
Diffstat (limited to 'cli/tests/testdata/test/uncaught_errors.out')
-rw-r--r--cli/tests/testdata/test/uncaught_errors.out59
1 files changed, 0 insertions, 59 deletions
diff --git a/cli/tests/testdata/test/uncaught_errors.out b/cli/tests/testdata/test/uncaught_errors.out
deleted file mode 100644
index a52f95d57..000000000
--- a/cli/tests/testdata/test/uncaught_errors.out
+++ /dev/null
@@ -1,59 +0,0 @@
-running 3 tests from ./test/uncaught_errors_1.ts
-foo 1 ... FAILED ([WILDCARD])
-foo 2 ... ok ([WILDCARD])
-foo 3 ...
-Uncaught error from ./test/uncaught_errors_1.ts FAILED
-foo 3 ... cancelled (0ms)
-running 3 tests from ./test/uncaught_errors_2.ts
-bar 1 ... ok ([WILDCARD])
-bar 2 ... FAILED ([WILDCARD])
-bar 3 ... FAILED ([WILDCARD])
-Uncaught error from ./test/uncaught_errors_3.ts FAILED
-
- ERRORS
-
-foo 1 => ./test/uncaught_errors_1.ts:1:6
-error: Error: foo 1 message
- throw new Error("foo 1 message");
- ^
- at [WILDCARD]/test/uncaught_errors_1.ts:2:9
-
-./test/uncaught_errors_1.ts (uncaught error)
-error: (in promise) Error: foo 3 message
- Promise.reject(new Error("foo 3 message"));
- ^
- at [WILDCARD]/test/uncaught_errors_1.ts:8:18
-This error was not caught from a test and caused the test runner to fail on the referenced module.
-It most likely originated from a dangling promise, event/timeout handler or top-level code.
-
-bar 2 => ./test/uncaught_errors_2.ts:3:6
-error: Error: bar 2
- throw new Error("bar 2");
- ^
- at [WILDCARD]/test/uncaught_errors_2.ts:4:9
-
-bar 3 => ./test/uncaught_errors_2.ts:6:6
-error: Error: bar 3 message
- throw new Error("bar 3 message");
- ^
- at [WILDCARD]/test/uncaught_errors_2.ts:7:9
-
-./test/uncaught_errors_3.ts (uncaught error)
-error: (in promise) Error: baz
-throw new Error("baz");
- ^
- at [WILDCARD]/test/uncaught_errors_3.ts:1:7
-This error was not caught from a test and caused the test runner to fail on the referenced module.
-It most likely originated from a dangling promise, event/timeout handler or top-level code.
-
- FAILURES
-
-foo 1 => ./test/uncaught_errors_1.ts:1:6
-./test/uncaught_errors_1.ts (uncaught error)
-bar 2 => ./test/uncaught_errors_2.ts:3:6
-bar 3 => ./test/uncaught_errors_2.ts:6:6
-./test/uncaught_errors_3.ts (uncaught error)
-
-FAILED | 2 passed | 6 failed ([WILDCARD])
-
-error: Test failed