Re: [gobo-eiffel-develop] Suggestion for getest

[Eric B. <er...@go...>]

Dear Glenn,

> Would it make sense to add a command line option to getest to just execute
> the "Preparing Test Cases" step rather than all of the steps at once? In
> fact, an option to run each of the steps selectively would be useful.
> 
> This would make is easier to develop test harnesses using an IDE, such as
> EiffelBench. I could then develop the test harness code in the IDE, generate
> the test harnesses using getest and execute the test harness in the IDE.

As I said in the doc of 'getest', I borrowed almost everything
from Jim Weirich's 'eunit' tool. In 'eunit' there are such
command-line options but when I wrote 'getest' I was not sure
whether they were really useful. Well, your message tends to
prove that they are. Therefore I just added the following command
line options to 'getest':

  -g for testcase generation only
  -c for testcase compilation only
  -e for testcase execution only

You can also combine these options, for example '-g -c' will
generate and compile the testcase classes, but not execute it.
Furthermore if none of these new options are specified, it will
be equivalent to '-g -c -e' for backward compatibility purposes.
(Please note that my command-line parser in 'getest' is very
rudimentary and therefore the shortcut '-gc' instead of '-g -c'
or '-gce' instead of '-g -c -e' is not recognized yet.)

In order to take advantage of these new command-line options
you will need to checkout the following class:

  gobo/src/getest/getest.e

from CVS at:

  https://sourceforge.net/cvs/?group_id=24591

and then recompile 'getest' using the Ace files in the directory:

  $GOBO/src/getest

PS: This is only the first version of 'getest', therefore there
are probably things to be improved. In particular new assertion
checks could be added to TS_ASSERTION_ROUTINES. Suggestions
welcome.

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com