Closed
Description
🐛 Bug description
when running wasm-pack test --firefox
I receive the following output
[1/7] Checking `rustc` version...
[2/7] Checking crate configuration...
[3/7] Adding WASM target...
info: component 'rust-std' for target 'wasm32-unknown-unknown' is up to date
[4/7] Compiling tests to WASM...
Finished dev [unoptimized + debuginfo] target(s) in 0.05s
wasm-bindgen 0.2.25
[5/7] wasm-bindgen already installed...
[6/7] Getting geckodriver...
[7/7] Running tests in Firefox...
Finished dev [unoptimized + debuginfo] target(s) in 0.06s
Running target/wasm32-unknown-unknown/debug/deps/keycap_rs-882a5a05a48b2dd4.wasm
no tests to run!
Running target/wasm32-unknown-unknown/debug/deps/wasm-c9e8681418ea5a41.wasm
Int
Note that interactive mode is enabled because `NO_HEADLESS`
is specified in the environment of this process. Once you're
done with testing you'll need to kill this server with
/ Ctrl-C.
Notice the cut off "Int " line above the NO_HEADLESS message.
🤔 Expected Behavior
When running NO_HEADLESS=1 cargo test --target wasm32-unknown-unknown
(with the wasm-bindgen-test-runner in .cargo/config) I see the expected URL line
Finished dev [unoptimized + debuginfo] target(s) in 0.06s
Running target/wasm32-unknown-unknown/debug/deps/keycap_rs-882a5a05a48b2dd4.wasm
no tests to run!
Running target/wasm32-unknown-unknown/debug/deps/wasm-c9e8681418ea5a41.wasm
Interactive browsers tests are now available at http://127.0.0.1:8000
Note that interactive mode is enabled because `NO_HEADLESS`
is specified in the environment of this process. Once you're
done with testing you'll need to kill this server with
Ctrl-C.
Notice the "are now available at ..." line present
👟 Steps to reproduce
Run wasm-pack test
without --headless
🌍 Your environment
wasm-pack version: 0.5.1
wasm-bindgen-test: 0.2.25
rustc version: 1.31.0-nightly (424a749a0 2018-10-21)