https://docs.nose2.io/en/latest/configuration.html#configuration-files is missing a bit of crucial information: what is the name of the .ini file? It looks like it can be both "unittest.cfg" or "nose2.cfg" if I read the code. Is this correct?

Suites like gcov works well if I execute many binaries (or the same binary with different arguments) in parallel, does kcov support this too? In particular, I'm interested in bash coverage.

For example, to have two scripts that source common.sh, and I execute them in two different shells, will the common.sh merged reports be OK? If not, what parts of kcov should be modified to support it?

Th

In the documentation the description of how to use mocks is focused on injecting them in the tested functions.

An important use case is that the code under test is actually calling functions that are not injected but linked. There are a couple of cases here that we should document:

• calling your own linked functions
• calling library functions

And there are a couple of mechanics to hand

Previously, when used under Prove, assert-that call produced a nice output:

TEST> (assert-that task
                   (has-slots 'title "The title "))
  ✓ Has slots:
      TITLE = "The title "

However, for Rove, it just returns t or nil.

We need to create a helper for a demonstration of a matcher without a call to assert-that. And to rewrite all docstrings to use