El 02/09/2016 a las 15:24, Graeme Geldenhuys escribió:
information will pollute the generated XML to stdout.
Why not specify a output file for the generated XML, instead of letting
it go to stdout. Run the FPCUnit console test application with the -h
parameter to see what options are
On 2016-09-02 14:14, José Mejuto wrote:
> but if I use the writeln this
> information will pollute the generated XML to stdout.
Why not specify a output file for the generated XML, instead of letting
it go to stdout. Run the FPCUnit console test application with the -h
parameter to see what
El 02/09/2016 a las 14:39, Graeme Geldenhuys escribió:
If the tests may show some kind of progress information
I'm assuming you are talking about FPCUnit?
If so, there is already a test progress listener implemented in the form
of the TProgressWriter class (see the consoletestrunner.pas
On 2016-09-02 00:48, José Mejuto wrote:
> If the tests may show some kind of progress information
I'm assuming you are talking about FPCUnit?
If so, there is already a test progress listener implemented in the form
of the TProgressWriter class (see the consoletestrunner.pas unit).
Simply run
On Fri, 2 Sep 2016, José Mejuto wrote:
Hello,
In the TTestSuite class when process is finished a XML is written to
stdout. If the tests may show some kind of progress information, for
manually run tests, this information must be in stdout, stderr, is there
a specific method available for
Hello,
In the TTestSuite class when process is finished a XML is written to
stdout. If the tests may show some kind of progress information, for
manually run tests, this information must be in stdout, stderr, is there
a specific method available for progress output ?
Cheers,
José
