mirror of
https://github.com/denoland/deno.git
synced 2025-03-04 01:44:26 -05:00
3b6b75bb46
This commit introduces two new buffer wrapper types to `deno_core`. The main benefit of these new wrappers is that they can wrap a number of different underlying buffer types. This allows for a more flexible read and write API on resources that will require less copying of data between different buffer representations. - `BufView` is a read-only view onto a buffer. It can be backed by `ZeroCopyBuf`, `Vec<u8>`, and `bytes::Bytes`. - `BufViewMut` is a read-write view onto a buffer. It can be cheaply converted into a `BufView`. It can be backed by `ZeroCopyBuf` or `Vec<u8>`. Both new buffer views have a cursor. This means that the start point of the view can be constrained to write / read from just a slice of the view. Only the start point of the slice can be adjusted. The end point is fixed. To adjust the end point, the underlying buffer needs to be truncated. Readable resources have been changed to better cater to resources that do not support BYOB reads. The basic `read` method now returns a `BufView` instead of taking a `ZeroCopyBuf` to fill. This allows the operation to return buffers that the resource has already allocated, instead of forcing the caller to allocate the buffer. BYOB reads are still very useful for resources that support them, so a new `read_byob` method has been added that takes a `BufViewMut` to fill. `op_read` attempts to use `read_byob` if the resource supports it, which falls back to `read` and performs an additional copy if it does not. For Rust->JS reads this change should have no impact, but for Rust->Rust reads, this allows the caller to avoid an additional copy in many scenarios. This combined with the support for `BufView` to be backed by `bytes::Bytes` allows us to avoid one data copy when piping from a `fetch` response into an `ext/http` response. Writable resources have been changed to take a `BufView` instead of a `ZeroCopyBuf` as an argument. This allows for less copying of data in certain scenarios, as described above. Additionally a new `Resource::write_all` method has been added that takes a `BufView` and continually attempts to write the resource until the entire buffer has been written. Certain resources like files can override this method to provide a more efficient `write_all` implementation. |
||
|---|---|---|
| .. | ||
| abort_controller_test.ts | ||
| blob_test.ts | ||
| body_test.ts | ||
| broadcast_channel_test.ts | ||
| buffer_test.ts | ||
| build_test.ts | ||
| cache_api_test.ts | ||
| chmod_test.ts | ||
| chown_test.ts | ||
| console_test.ts | ||
| copy_file_test.ts | ||
| custom_event_test.ts | ||
| dir_test.ts | ||
| dom_exception_test.ts | ||
| error_stack_test.ts | ||
| error_test.ts | ||
| esnext_test.ts | ||
| event_target_test.ts | ||
| event_test.ts | ||
| fetch_test.ts | ||
| ffi_test.ts | ||
| file_test.ts | ||
| filereader_test.ts | ||
| files_test.ts | ||
| flash_test.ts | ||
| flock_test.ts | ||
| fs_events_test.ts | ||
| get_random_values_test.ts | ||
| globals_test.ts | ||
| headers_test.ts | ||
| http_test.ts | ||
| internals_test.ts | ||
| intl_test.ts | ||
| io_test.ts | ||
| link_test.ts | ||
| make_temp_test.ts | ||
| message_channel_test.ts | ||
| metrics_test.ts | ||
| mkdir_test.ts | ||
| navigator_test.ts | ||
| net_test.ts | ||
| network_interfaces_test.ts | ||
| opcall_test.ts | ||
| os_test.ts | ||
| path_from_url_test.ts | ||
| performance_test.ts | ||
| permissions_test.ts | ||
| process_test.ts | ||
| progressevent_test.ts | ||
| promise_hooks_test.ts | ||
| read_dir_test.ts | ||
| read_file_test.ts | ||
| read_link_test.ts | ||
| read_text_file_test.ts | ||
| README.md | ||
| real_path_test.ts | ||
| ref_unref_test.ts | ||
| remove_test.ts | ||
| rename_test.ts | ||
| request_test.ts | ||
| resources_test.ts | ||
| response_test.ts | ||
| signal_test.ts | ||
| spawn_test.ts | ||
| stat_test.ts | ||
| stdio_test.ts | ||
| streams_deprecated.ts | ||
| structured_clone_test.ts | ||
| symlink_test.ts | ||
| sync_test.ts | ||
| test_util.ts | ||
| testing_test.ts | ||
| text_encoding_test.ts | ||
| timers_test.ts | ||
| tls_test.ts | ||
| truncate_test.ts | ||
| tty_color_test.ts | ||
| tty_test.ts | ||
| umask_test.ts | ||
| url_search_params_test.ts | ||
| url_test.ts | ||
| urlpattern_test.ts | ||
| utime_test.ts | ||
| version_test.ts | ||
| wasm_test.ts | ||
| webcrypto_test.ts | ||
| webgpu_test.ts | ||
| websocket_test.ts | ||
| worker_permissions_test.ts | ||
| worker_types.ts | ||
| write_file_test.ts | ||
| write_text_file_test.ts | ||
Deno runtime tests
Files in this directory are unit tests for Deno runtime.
Testing Deno runtime code requires checking API under different runtime
permissions. To accomplish this all tests exercised are created using
Deno.test() function.
import {} from "./test_util.ts";
Deno.test(function simpleTestFn(): void {
// test code here
});
Deno.test(
{
ignore: Deno.build.os === "windows",
permissions: { read: true, write: true },
},
function complexTestFn(): void {
// test code here
},
);
Running tests
There are two ways to run unit_test_runner.ts:
# Run all tests.
target/debug/deno test --allow-all --unstable --location=http://js-unit-tests/foo/bar cli/tests/unit/
# Run a specific test module
target/debug/deno test --allow-all --unstable --location=http://js-unit-tests/foo/bar cli/tests/unit/files_test.ts
Http server
target/debug/test_server is required to run when one's running unit tests.
During CI it's spawned automatically, but if you want to run tests manually make
sure that server is spawned otherwise there'll be cascade of test failures.