Hi,
I downloaded the new FPC version, 2.1.4, for the Intel Mac platform
to try it. When I try to install it the installer refuses to proceed,
saying that "this package contains only Intel binaries which cannot
be used on a PowerPC-based Macintosh. Install the PowerPC version of
FPC instea
On 5/21/07, Dean Zobec <[EMAIL PROTECTED]> wrote:
creating other suites and building the tree. So your unit is very handy
for this and spares some typing.
Yeah, I have now grouped the tiOPF tests into the following suites.
Non-Persistent Tests and then one testsuite per registered persistant
l
Michael Van Canneyt pravi:
>
> The good news is that fpcunit is scheduled for documentation after fcl-base
> and before fcl-db. The bad news is that there are still 12 units to be
> documented in fcl-base. Which is about 1/3 of the total number of units
> in fcl-base.
>
> We'll get there. Slo
Graeme Geldenhuys pravi:
> Looking into the DUnit code I found the reason for passing in the
> name. It's actually a Suite Path used to automatically create
> TTestSuites for you so you can better group you tests case in a
> hierarchy. You would use it if you don't want the registered test
> case
On Mon, 21 May 2007, Graeme Geldenhuys wrote:
> > TTest is an abstract class, TTestSuite is a composite pattern. Just look
> > at the JUnit documentation, here you can find a UML diagram:
>
> Thanks, I'll take a look at those links. I'm sure they will come in handy.
>
> >
> > Still, it's not a
On 5/21/07, Dean Zobec <[EMAIL PROTECTED]> wrote:
The ATest parameter can be a TTestCase or a TTestSuite
After reading some more docs on DUnit (which is also a port of JUnit)
I found they implemented the Composite pattern. Looking a bit closer
to the FPCUnit code I came to the same conclusion
Graeme,
> Hi,
>
> When would you use TestSuiteName and when TestName?
TestSuiteName is the name of the TestSuite (parent) that contains the Test
>
> For example, the following I think is wrong.
>
> constructor TTestSuite.Create(AName: string);
> begin
> Create();
> FName := AName;
> end;
>
>
I attached the unit I defined the two functions in. Please note, this
is not a patch, it is just to show the implementation of the functions
(for review). If it will make the 2.2 release, I will create a patch
(and be able to delete my own unit).
Graeme.
On 5/21/07, Graeme Geldenhuys <[EMAIL
Hi,
Would this feature make the 2.2 release if I submit a patch? I need to
know for my own projects. It is only two new functions. It allows you
to register tests and automatically builds the TestSuite structure for
you... Before you had to manually create the TestSuite's.
See the attached imag
Hi,
When would you use TestSuiteName and when TestName?
For example, the following I think is wrong.
constructor TTestSuite.Create(AName: string);
begin
Create();
FName := AName;
end;
Shouldn't this set the FTestSuiteName field?
Now if I do a TestSuite.TestSuiteName it doesn't return FName,
Hi,
I know the latest 2.1.x FPCUnit can handle nested or grouped
testsuites, but how do you actually register those?
For example:
I want to split my tests suites into two groups. One group that
requires DB connections and the other group that doesn't. This will
then hopefully allow me to run e
On Sun, 20 May 2007, M. Utku Karataş wrote:
> Hi everyone,
>
> I am using version 2.1.1 on Linux and calling this procedure in a thread:
>
> procedure TestNullRef;
> var p: ^integer;
> begin
>p := nil;
>try
>p^ := 13; // now this should raise exc!
>ShowMessage(IntToStr(
12 matches
Mail list logo
