Documentation and critical functional issues

[alekdavis]

Just started looking at the CLI usage and want to report a couple of issues (mostly about the documentation page but also about functionality):

• There are no examples of the CLI usage. The Example section, shows the test/request example, but it does not have any examples of the actual CLI usage (the examples and guide links in this section also do not point to any CLI examples, although if you scroll down the guide post, which is titled Overview and click the CLI link at the bottom of the post, then you can find a some basic examples). It would be nice to have more and easier to find examples of the CLI usage.
• What does the --quiet flag mean? (Shouldn't there be a -q shortcut?)
• How do you pass multiple values to a command-line switch? I think you just need to separate them by spaces, but it's not covered and I did not find any examples. It would be nice to have it cleared.
• It looks like when you do not pass any parameter to the -o or --output-failed switches it will output everything, but it would be nice if this were documented (I had to try it to make sure).
• It would be nice to have the counters of skipped (and maybe disabled, but disabled are not important) tests in the summary.
• Counters in the JUNIT output do not make much sense (or maybe I'm not reading them correctly).

THIS ONE IS CRITICAL:

• The conditional cancelation logic does not work. If I run tests in a file with the -a switch (meaning to run all tests, except explicitly disabled via @disabled), then if any test is cancelled (via $cancel), then it will not execute any other tests after the first encountered cancellation condition, not even the tests with no dependencies).

Overall, the CLI looks pretty good.

[alekdavis]

I created a separate issue to track the $cancel CLI logic bug here *since it is a critical bug, unlike docs): #808