Something like:
https://github.com/rust-random/getrandom/blob/8861a62a25cafad5a0cc5bc1f16715865b9d4456/tests/mod.rs#L4-L5

#[cfg(all(feature = "wasm_js", target_arch = "wasm32", target_os = "unknown"))]
use wasm_bindgen_test::wasm_bindgen_test as test;

doesn't work (instead of rusqlite-test-helper) ?

doesn't work (instead of rusqlite-test-helper) ?

it requires adding this line of configuration to every test mod, which may not be the most convenient approach.

% rg -F 'mod test' | wc -l
      41

vs

% rg -F '#[test]' | wc -l
     275

We don't have to think about wasm each time we add a test function (only when we add a test module)...

We don't have to think about wasm each time we add a test function (only when we add a test module)...

done

hmm, continuous-integration/appveyor/pr failure doesn't seem related to this PR

hmm, continuous-integration/appveyor/pr failure doesn't seem related to this PR

Yep, you can ignore it.
(I will try to merge your PR this week)

#[cfg(not(all(target_family = "wasm", target_os = "unknown")))]
#[deprecated(since = "0.33.0", note = "use trace_v2 instead")]
pub fn trace(&mut self, trace_fn: Option<fn(&str)>) {}

#[cfg(not(all(target_family = "wasm", target_os = "unknown")))]
#[deprecated(since = "0.33.0", note = "use trace_v2 instead")]
pub fn profile(&mut self, profile_fn: Option<fn(&str, Duration)> {}

sqlite_wasm_rs no longer bindgen sqlite3_trace and sqlite3_profile, so I configured them.

Almost 5 years later
Thanks.