From 64045ebc7a4e1c9f77204ffe35563134a453a7c6 Mon Sep 17 00:00:00 2001 From: Matt Mastracci Date: Tue, 29 Aug 2023 13:02:54 -0600 Subject: chore(cli): use NPM_CONFIG_REGISTRY for all tests (#20320) We never want tests to hit the real npm registry because this causes test flakes. In addition, we set a sentinal "unset" value for `NPM_CONFIG_REGISTRY` to ensure that all tests requiring npm go through the test server. --- cli/tests/integration/check_tests.rs | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'cli/tests/integration/check_tests.rs') diff --git a/cli/tests/integration/check_tests.rs b/cli/tests/integration/check_tests.rs index 54e93ca35..253ccf767 100644 --- a/cli/tests/integration/check_tests.rs +++ b/cli/tests/integration/check_tests.rs @@ -86,13 +86,17 @@ itest!(check_static_response_json { itest!(check_node_builtin_modules_ts { args: "check --quiet check/node_builtin_modules/mod.ts", output: "check/node_builtin_modules/mod.ts.out", + envs: env_vars_for_npm_tests(), exit_code: 1, + http_server: true, }); itest!(check_node_builtin_modules_js { args: "check --quiet check/node_builtin_modules/mod.js", output: "check/node_builtin_modules/mod.js.out", + envs: env_vars_for_npm_tests(), exit_code: 1, + http_server: true, }); itest!(check_no_error_truncation { -- cgit v1.2.3