Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://rustwasm.github.io/docs/wasm-pack/commands/test.html below:

test - Hello wasm-pack!

1. 1. Introduction
2. 2. Quickstart
3. 3. Prerequisites
4. 1. 3.1. npm (optional)
   2. 3.2. considerations
   3. 3.3. Non-rustup setups
5. 4. Commands
6. 1. 4.1. new
   2. 4.2. build
   3. 4.3. test
   4. 4.4. pack and publish
   5. 4.5. init (DEPRECATED)
7. 5. Tutorials
8. 1. 5.1. Hybrid applications with Webpack
   2. 1. 5.1.1. Getting started
      2. 5.1.2. Using your library
   3. 5.2. npm browser packages
   4. 1. 5.2.1. Getting started
      2. 1. 5.2.1.1. Manual Setup
      3. 5.2.2. Template deep dive
      4. 1. 5.2.2.1. Cargo.toml
         2. 5.2.2.2. src/lib.rs
         3. 5.2.2.3. src/utils.rs
         4. 5.2.2.4. wee_alloc
         5. 5.2.2.5. tests/web.rs
      5. 5.2.3. Building your project
      6. 5.2.4. Testing your project
      7. 5.2.5. Packaging and publishing
      8. 5.2.6. Using your library
9. 6. Cargo.toml Configuration
10. 7. Contributing

The wasm-pack test command wraps the wasm-bindgen-test-runner CLI allowing you to run wasm tests in different browsers without needing to install the different webdrivers yourself.

wasm-pack test --help

The wasm-pack test command can be given an optional path argument.

This path should point to a directory that contains a Cargo.toml file. If no path is given, the test command will run in the current directory.

# Run tests for the current directory's crate
wasm-pack test

# Run tests for a specified crate
wasm-pack test crates/crate-in-my-workspace

The test command accepts an optional profile argument: --release.

If none is supplied, then a debug test build will be used.

Choose where to run your tests by passing in any combination of testing environment flags.

--headless is useful for running browser tests in a headless browser as part of a CI process.

wasm-pack test --node --firefox --chrome --safari --headless

The test command can pass extra options straight to cargo test even if they are not supported in wasm-pack.

To use them simply add the extra arguments at the very end of your command, just as you would for cargo test.

cargo test -h for a list of all options that you can pass through.

When debugging a specific issue, you may find yourself wanting to run a subset of tests, instead of your entire suite of tests.

Here are a few examples of how to run a subset of your tests:

# Example directory structure
$ tree crates/foo
├── Cargo.toml
├── README.md
├── src
│   ├── diff
│   │   ├── diff_test_case.rs
│   │   └── mod.rs
│   ├── lib.rs
└── tests
    ├── diff_patch.rs
    └── node.rs

# Run all tests in tests/diff_patch.rs in Firefox
wasm-pack test crates/foo --firefox --headless --test diff_patch

# Run all tests in tests/diff_patch.rs that contain the word "replace"
wasm-pack test crates/foo --firefox --headless --test diff_patch replace

# Run all tests inside of a `tests` module inside of src/lib/diff.rs
wasm-pack test crates/foo --firefox --headless --lib diff::tests

# Same as the above, but only if they contain the word replace
wasm-pack test crates/foo --firefox --headless --lib diff::tests::replace

Note that you can also filter tests by location in which they're supposed to run. For example:

# Run all tests which are intended to execute in Node.js
wasm-pack test --node

# Run all tests which are intended to be executed in a browser
wasm-pack test --firefox --headless

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4