On 9 nov 2006, at 13:33, [EMAIL PROTECTED] wrote:
Wait a minute But you need a stable enough compiler to compile the
testsuite right?
You need a lot more compiler functionality to compile the fcl than to
compile individual tests (not to mention that a problem which occurs
when compili
On Thu, 9 Nov 2006, [EMAIL PROTECTED] wrote:
> >> On 09/11/06, Florian Klaempfl <[EMAIL PROTECTED]> wrote:
> >>> First, I would prefer a patch to the fpcunit which makes the unit
> >>> itself
> >>> indenpendend from other stuff (xml) so it can be used in the fpc
> >>> test suite :)
> >>
> >> The
On 09/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Wait a minute But you need a stable enough compiler to compile the
testsuite right?
That's what I wast trying to get at... You need a compiler already.
As to the order of how things are compiler and tested (RTL, FCL, etc)
I have no i
>> On 09/11/06, Florian Klaempfl <[EMAIL PROTECTED]> wrote:
>>> First, I would prefer a patch to the fpcunit which makes the unit
>>> itself
>>> indenpendend from other stuff (xml) so it can be used in the fpc
>>> test suite :)
>>
>> The xml used is the xmlwriter unit - part of FPC. Is this a prob
On Thu, 9 Nov 2006, Jonas Maebe wrote:
>
> On 9 nov 2006, at 11:47, Graeme Geldenhuys wrote:
>
> >On 09/11/06, Florian Klaempfl <[EMAIL PROTECTED]> wrote:
> > >First, I would prefer a patch to the fpcunit which makes the unit itself
> > >indenpendend from other stuff (xml) so it can be used in
On 9 nov 2006, at 12:49, Graeme Geldenhuys wrote:
Ok, so if the OutputFactory idea is also not going to work. Why not
try something completely different. What if every test suite compiled
to a .dll or .so file - nothing more. The fpcUnit executable compiled
previously with a stable compiler a
On 09/11/06, Jonas Maebe <[EMAIL PROTECTED]> wrote:
> The xml used is the xmlwriter unit - part of FPC. Is this a problem?
The problem is that the xml stuff must be built before you can run
the testsuite with fpcunit tests included (since the fpcunit package
depends on the xml stuff). This mean
On 9 nov 2006, at 11:47, Graeme Geldenhuys wrote:
On 09/11/06, Florian Klaempfl <[EMAIL PROTECTED]> wrote:
First, I would prefer a patch to the fpcunit which makes the unit
itself
indenpendend from other stuff (xml) so it can be used in the fpc
test suite :)
The xml used is the xmlwriter
On Thu, 9 Nov 2006, Florian Klaempfl wrote:
> First, I would prefer a patch to the fpcunit which makes the unit itself
> indenpendend from other stuff (xml) so it can be used in the fpc test suite :)
The unit fpcunit is independent of XML ?
The package as a whole is dependent on XML, this is c
On 09/11/06, Florian Klaempfl <[EMAIL PROTECTED]> wrote:
First, I would prefer a patch to the fpcunit which makes the unit itself
indenpendend from other stuff (xml) so it can be used in the fpc test suite :)
The xml used is the xmlwriter unit - part of FPC. Is this a problem?
Test output is o
First, I would prefer a patch to the fpcunit which makes the unit itself
indenpendend from other stuff (xml) so it can be used in the fpc test suite :)
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinf
On 09/11/06, Vincent Snijders <[EMAIL PROTECTED]> wrote:
> Number of run tests: 20
> Number of errors:0
> Number of failures: 0
IMHO the 'Number of ...' should be enabled with a new -s (and --summary)
switch
That makes sence, yes.
> Hierarchy view for test listing in XML. The XSLT fil
Graeme Geldenhuys schreef:
Dean,
As requested. Here goes...
Let me know what you think of Item 1? If you wanted to start with any
of these, Item 1 would be good. :-)
===
Item 1
===
I have an idea on improving the console runner outpu
13 matches
Mail list logo
