How to use LuaCov with mini.test?

[MunifTanjim]

How to use LuaCov with mini.test?

I tried require-ing LuaCov by doing pcall(require, "luacov") at the top of the test file. But it doesn't generate luacov.stats.out file after test is run.

[echasnovski]

Not quite sure, as I don't use it at all. It might be even impossible for how 'mini.test' recommends to do tests (each one in a separate new child process), so not sure.

[echasnovski]

Does mini.test spawn child process by default?
No, it doesn't.

---

Not sure, maybe it has something to do with the fact that 'mini.test' doesn't actually run tests when they are sourced. It first collects them in a special table and then executes its content.

[powerman]

Any progress on this? It will be sad to go back to plenary.test_harness just because of this issue. 😞

[echasnovski]

Any progress on this? It will be sad to go back to plenary.test_harness just because of this issue. 😞

There is no work done or planned for LuaCov compatibility with 'mini.test', I am afraid. Mostly because I can not reasonably imagine how this would work with the suggested way of running tests (each in a separate child process).

[powerman]

I've no idea about luacov, but I did similar things with coverage in Go - it was quite easy to merge coverage reports generated from different processes into common report. Maybe something like that will solve this issue for mini.test child processes too.

[echasnovski]

... it was quite easy to merge coverage reports generated from different processes into common report. Maybe something like that will solve this issue for mini.test child processes too.

Reserving so much effort in 'mini.test' itself for it to work with third party tool is definitely out of scope. The module is already pretty big as is.