mirror of
https://github.com/denoland/deno.git
synced 2024-11-28 16:20:57 -05:00
f5e46c9bf2
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.
18 lines
515 B
Markdown
18 lines
515 B
Markdown
# npm test data
|
|
|
|
This folder contains test data for npm specifiers.
|
|
|
|
## Registry
|
|
|
|
The registry is served by the test server (server in test_util) at
|
|
http://localhost:4545/npm/registry/ via the `./registry` folder.
|
|
|
|
### Updating with real npm packages
|
|
|
|
1. Set the `DENO_TEST_UTIL_UPDATE_NPM=1` environment variable
|
|
2. Run the test and it should download the packages.
|
|
|
|
### Using a custom npm package
|
|
|
|
1. Add the custom package to `./registry/@denotest`
|
|
2. Reference `npm:@denotest/<your-package-name>` in the tests.
|