Begin forwarded message:
From: Dean Zobec <[EMAIL PROTECTED]>
Date: Fri 10 Nov 2006 00:04:44 GMT+01:00
To: Florian Klaempfl <[EMAIL PROTECTED]>, Michael Van Canneyt
<[EMAIL PROTECTED]>, Jonas Maebe <[EMAIL PROTECTED]>
Subject: Re: Fwd: [fpc-pascal] fpcUnit todo list
Michael Van Canneyt ha scritto:
On Thu, 9 Nov 2006, Florian Klaempfl wrote:
Jonas Maebe schrieb:
The easiest thing to do is to include fpcunit itself in fcl/inc.
All the units around it can be done in fcl/fpcunit, which is
built at
a later stage.
Michael.
I agree with this.
This arises a fundamental question: should the tests for all
package (non
rtl/compiler!) go into fpc/tests/<package> or should they be in
fpc/<package>/test and being executed by make tests in fpc/? At
least it
It must be fpc/package/tests.
Peter and I decided to build support in the packager for this, so
you can
- download
- compile
- test
- install
a package...
Michael.
Good idea ! :)
I agree, the first thought I had was to put them in fpc/<package>/tests
directory, they should be somehow close to the production code. The
support in the packager is absolutely great! But it would be also useful
that the main build process would be able to build all the tests in a
single runner program and run them at once. I think that even with a
very large number of tests the suite of all unit tests could be built
and run in less than a minute considering that is a single program (of
course a configuration file could be added to be able to skip some tests
that take more time to run).
Dean
P.s Michael, did you receive my mail with the attached packages tests
you've asked for?
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
