Pascal Grange

Hi @poWer4aiX, First, thanks for using bash_unit and for your PR! I really appreciate the effort you put into this. You're raising two concerns I can relate a lot with:...

Trying to make a non technical person read that test, I ended up with the following proposal, in plain bash, which, I think, is even simpler to read: ``` test_calling_wc_without_any_arguments_should_also_count_nb_lines()...

Hi @poWer4aiX , > I'm not a friend of calling the "unit under test" more than once in a test I probably spent too much time trying to do functional...

Hi @poWer4aiX , bash_unit can output the results in different formats. This is handled in a sort of _extension_ way: * The [test_format](https://github.com/pgrange/bash_unit/blob/main/bash_unit#L370C1-L370C12) function sets up the `notify_*` functions so...

Hi @jbergstroem and thanks for using bash_unit. It seems `kcov` has an interesting way of encapsulating a shell script before analyzing coverage. For instance, I noted that it just ignores...

FYI, I have way more chance with `bashcov`. For instance with the getting_started project: ```bash git clone https://github.com/bash-unit/getting_started.git cd getting_started bashcov bash_unit tests/test_* open coverage/index.html ``` It's interesting to observe,...

> > Thanks for taking a look and exploring options as well. I started with bashcov too, but the output is mostly html where i am looking for the actual...