Ari

Can we have an update on this?

I looked into this a bit and tried to simply compile a test using `minicov`. ```rust wasm_bindgen_test::wasm_bindgen_test_configure!(run_in_browser); #[cfg(test)] mod test { #[wasm_bindgen_test::wasm_bindgen_test] async fn test_foo() { assert!(true); } } ```...

I believe that the issue is that we are trying to measure coverage of the `describe` function created by `#[wasm_bindgen]`. The profiler doesn't know nor care that this macro expanded...

I compiled rustc locally and removed the feature gate of `#[coverage(off)]`. Unfortunately, I wasn't able to get the desired results. For now, what works is simply ignoring any `i64` related...

I've been able to create a coverage report for a test (yay). However I simply printed the profdata to stdout and parsed it afterwards from there. The remaining crucial question...

> We could built that into wasm-bindgen-test-runner, which hosts a server Oh, that's convenient. I'll add two endpoints then. One that is run after every test that appends the coverage...

Pinging @daxpedda

> Yo, exciting stuff! Is this already in a state where I can try it out? Not yet, the questions covered really stop this from being viable until they're resolved....

> Would really like to figure out why #[coverage(off)] doesn't work. I don't know enough about this part of wasm-bindgen to say for sure this won't cause problems in the...

Verifying the RUSTFLAGS on every run seems a bit excessive.If we are already printing a warning about using the coverage feature we could simply print a hint linking to the...