Lines Matching refs:test

1 # test-programs
3 This crate contains many different binaries which are built into Wasm test
6 Each file in `./src/bin/` is built into a distinct test binary. By convention,
7 the prefix before the first underscore in each binary is the name of the test
14 This suite is used for exercising `wasmtime`'s Rust APIs. Each test program in
17 These test programs are executed in `/crates/wasi/tests/api.rs`.
22 `wasmtime` native executable. Each test program in this suite has particular
27 These test programs are executed in `/tests/all/cli_tests.rs`.
31 This test suite is used for exercising the `wasmtime-wasi-http` crate. Each
32 test program in this suite is a component which exports the wasi-cli command
38 Each test program executor spawns a fresh tokio runtime on a unique local
39 socket which responds to the requests made by a single test program. This
40 socket address is passed to the test program using the `HTTP_SERVER`
43 These test programs are executed in `/crates/wasi-http/tests/all/sync.rs`
44 and `/crates/wasi-http/tests/all/async_.rs`, which test the synchronous and
50 This test suite is used for exercising the `wasmtime-wasi-nn` crate. It only
53 These test programs are executed in `crates/wasi-nn/tests/all.rs`.
59 the input of another instance. The test programs in this suite are passed
64 These test programs are executed in `/tests/all/cli_tests.rs`, which creates
66 descriptor set to the producer process stdout file descriptor. The test
72 and, additionally, provides test coverage of Wasi Preview 2 (aka Wasi 0.2)
77 test execution provides this by inheriting the host process stdio in some test
86   provided by the `wasi-common` crate. The test programs are executed
91   using the Wasi 0.2 implementation defined in that same crate. The test
101   host. The test programs are executed in
111 These test programs use `wit-bindgen` to generate bindings to Wasi 0.2
112 (invoked at the root of the `test-programs` crate), and then invoke those
113 bindings directly in each test. The modules created from these test programs
121 These tests are executed much like the component adapted preview1 test suite
124 ## Building and executing these test programs
126 These tests are built and consumed by way of the `test-programs-artifacts`
127 crate. `test-programs-artifacts` has a `build.rs` which compiles this crate
130 macros which iterate over the complete set of binary paths in a given test
133 The filesystem path to each Wasm Module built by `test-programs-artifacts`
138 The filesystem path to each Wasm Component built by `test-programs-artifacts`
145 Wasm Components are not built for the `nn` test suite. All other components
149 Each test suite is given an iterator macro in `test-programs-artifacts` named
153 the path of each test in the suite. You could do something very clever with
158 if a wasmtime developer adds a new test program, they also add a test which
165 #[test]