WASM tests do not catch the logs written by info!/warn!/...

[artemii235]

For example, I had to use log_tag! instead of info! here: https://github.com/KomodoPlatform/atomicDEX-API/commit/a53daabed076a0481f5bc18858b9239d3ccd3919#diff-608240539630bec8eb43b211b0b74ec3580b34dda66e339bac21c04b1db6da43R272-R277.

@sergeyboyko0791 Could you please tell if we can catch info!/... output in WASM tests, and how hard will it be?

[sergeyboyko0791]

I have two ideas on how to catch the logs and (most complex problem) to match them to a corresponding MmCtx instance:

1. Run the tests consequentially, not simultaneously. Then we can easily use a static log registry, clean it before each test.
2. Run each WASM test in as a separate process. Then they won't share the static data such as the static log registry.

Both ideas require changing the wasm test runner or using a custom one. I'll try to investigate what can be done.

[artemii235]

@sergeyboyko0791 This seems not easy. As this task is not a priority, you can postpone it indefinitely 🙂 Maybe we will have more ideas after some time.

[sergeyboyko0791]

I have also a workaround to implement the 1. point https://github.com/KomodoPlatform/atomicDEX-API/issues/1634#issuecomment-1411841050: We can implement a procedural macro #[mm2_wasm_test] that will do the following:

• Registers WASM log callback before the test. That's currently done manually, for example https://github.com/KomodoPlatform/atomicDEX-API/blob/e2f90465bf7a555d4efbcbfee32222109431ab71/mm2src/mm2_main/src/wasm_tests.rs#L71-L75
• If it's required (let's say if #[mm2_wasm_test(no_parallel)] not specified), manages to run the only this test at the same moment. This could also clear the static log registry, so we can catch the logs recorded by log::info macro.
• (The most important in my opinion) Set a timeout for each test. By default it could be 60s, but there should be the way to specify it. For example, #[mm2_wasm_test(timeout = 120)]. Currently, we don't have the way to detect the tests that were stuck. WASM bindgen runner doesn't provide such info, so I believe it could be very helpful.

@artemii235 what do you think?