Usage with `prove` would need more documentation about sharness HOT 6 CLOSED

man prove says this about arguments to tests:

It is possible to supply arguments to tests. To do so separate them from prove's own arguments with the arisdottle, '::'. For example
prove -v t/mytest.t :: --url http://example.com
would run t/mytest.t with the options '--url http://example.com'. When running multiple tests they will each receive the same arguments.

So you have to do it like prove :: -l. This is something about prove, not sharness.

The fact that prove counts SKIP tests as success is an issue of prove.

That is to say, maybe it would be worth emphasizing the limitations of using prove together with sharness

This is a limitation of prove, not prove+sharness.

and possibly cover alternatives as well to help the user choose.

I started writing my own tool: rove, but it doesn't even report the number of successful tests, as I'm not interested in that. I'm mostly interested in knowing if all the tests pass or not.

from sharness.

So you have to do it like prove :: -l

Damned I had missed that from the prove manpage (and it is not the place for discussing its structure ;) ).

This is something about prove, not sharness

This is a limitation of prove, not prove+sharness.

Sure, but still it could be useful to let users know that the Makefile driver is better than prove on this point -- as well as an example of passing options for tests. If you don't object can propose a PR.

from sharness.

Sure, but still it could be useful to let users know that the Makefile driver is better than prove on this point

"better" is a subjective value judgement, for me prove works perfectly fine.

If you don't object can propose a PR.

But a PR to change what? The README is supposed to be short and to the point. This information seems like it belongs to a wiki page.

from sharness.

But a PR to change what? The README is supposed to be short and to the point.

I'd think it could be helpful to add a short note to "Command-line options" about that peculiar prove test :: flags syntax.

from sharness.

OK. I changed my mind.

I wanted to keep the README as simple as possible as the previous maintainer intended. But to be honest I think sharness should interact seamlessly with testing harnesses, and prove is the most popular (or even the only truly known one) testing harness.

So I think a short explanation of how to use sharness with prove in the README could make sense.

Feel free to send a pull request for that.

from sharness.

The README already mentions prove, I've added a page in the wiki with more details about how to use it: Prove.

I think that should be enough.

from sharness.