oak-run command line

[Julian Reschke <ju...@gmx.de>]

Hi there,

the README says:

> The benchmark mode is used for executing various micro-benchmarks. It can
> be invoked like this:
>
>     $ java -jar oak-run-*.jar benchmark [options] [testcases] [fixtures]
>
> The following benchmark options (with default values) are currently supported:

which gives the impression that you don't need to specify the testcases, 
in which case I'd assume all tests are executed - which is not the case.

Shouldn't this say:

 >     $ java -jar oak-run-*.jar benchmark [options] testcases [fixtures]

then?

Best regards, Julian

Re: oak-run command line

[Jukka Zitting <ju...@gmail.com>]

Hi,

On Tue, Jun 10, 2014 at 4:22 PM, Julian Reschke <ju...@gmx.de> wrote:
> OK; in which case I'd propose to change the tool to return with a helpful
> error message :-)

+1 Works for me.

BR,

Jukka Zitting

Re: oak-run command line

[Julian Reschke <ju...@gmx.de>]

On 2014-06-10 16:24, Jukka Zitting wrote:
> Hi,
>
> On Tue, Jun 10, 2014 at 8:42 AM, Julian Reschke <ju...@gmx.de> wrote:
>> which gives the impression that you don't need to specify the testcases, in
>> which case I'd assume all tests are executed - which is not the case.
>
> Another (and IMHO more logical) way of looking at it is that if you
> specify no test cases, then no tests get executed. Same with the
> fixtures.

OK; in which case I'd propose to change the tool to return with a 
helpful error message :-)

Re: oak-run command line

[Jukka Zitting <ju...@gmail.com>]

Hi,

On Tue, Jun 10, 2014 at 8:42 AM, Julian Reschke <ju...@gmx.de> wrote:
> which gives the impression that you don't need to specify the testcases, in
> which case I'd assume all tests are executed - which is not the case.

Another (and IMHO more logical) way of looking at it is that if you
specify no test cases, then no tests get executed. Same with the
fixtures.

BR,

Jukka Zitting