Damn! I just created a new Console Test from Lazarus and see that it
has changed dramatically since I originally created my console test
apps. My wish has been answered, - I see we now have a
consoletestrunner unit. Dope! :-)
Graeme.
On 26/10/06, Graeme Geldenhuys <[EMAIL PROTECTED]> wrote:
On 26/10/06, Vincent Snijders <[EMAIL PROTECTED]> wrote:
> > Where as the TextRunner would most likely be used for nightly build
> > runs, which can output to a file. This is where the XSL command line
> > parameter might be more useful. Also being able to specify the XSL
> > file to be used in the command line parameter might be useful. (read
> > my private email for more details)
> >
>
> The console text runner in the components\fpcunit\console already adds a
> stylesheet. I will add the default stylesheet in the distribution (as
> long as it isn't with fpc).
>
> I will give the console runner a parameter for the style sheet.
Thanks Vincent! I haven't noticed the default style sheet, because my
console runner apps where created ages ago from the Lazarus
wizard/template.
Maybe I am doing this wrong! Is there another way I can create a
console test runner apps, that if updates are included in newer
revisions, that a recompile of my existing console runner app with get
those changes?
Currently my console runner app descends from TCustomApplication and
implements it's own parameter support. Must I descend from a
different class, or is there a ConsoleTestRunner (something like
GUITestRunner) unit I can include in my console test apps?
I can't remember, but how does DUnit handle this, or are they sitting
with the same problem? Maybe it is just me.. :-)
Regards,
- Graeme -
--
There's no place like 127.0.0.1
--
There's no place like 127.0.0.1
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
