I have/had several tests that took very long to run.
I have no figured out that between 50% and 80% of the time, went into
concatenating/formatting the message for "AssertEqual" (and related).
Yes, some of my tests now run in less than 20% of the original time.
That is
- Any concatenation my c
On Sat, 14 Jun 2025, Martin Frb via fpc-devel wrote:
I have/had several tests that took very long to run.
I have no figured out that between 50% and 80% of the time, went into
concatenating/formatting the message for "AssertEqual" (and related).
Yes, some of my tests now run in less than 20
On Jun 14, 2025 at 10:50:46 PM, Martin Frb via fpc-devel <
fpc-devel@lists.freepascal.org> wrote:
> I may... Need to find some time.
>
> Also, what do you think about overloading AssertEquals (and the like)
> taking
> AssertEqual(
> const AnFormatString: string;
> const AFormatData: array of
On 14/06/2025 15:44, Michael Van Canneyt via fpc-devel wrote:
I have heaps and heaps of testcases, but I've never felt the need to
investigate
the speed of the Assert* calls.
I wasn't actually looking at it... I found it by random chance.
I was trying to kcachegrind some of my code, and the
