Ant vs Java: batchtestserver, batchtest

[Vladimir Sitnikov <si...@gmail.com>]

Hi,

I see there's a bunch of tests written in Ant (see target
name="batchtestserver" and target name="batchtest")
It makes sense to rewrite the tests in Java / Groovy so the tests can
be run individually, the output could be improved, timeouts could be
added, etc, etc.
I don't really see the reason to use those Ant targets. I see no
reasons to migrate the targets to Gradle either.

Any objections on that?
Does anybody volunteer to rework those targets into a test class?

Vladimir

Re: Ant vs Java: batchtestserver, batchtest

[sebb <se...@gmail.com>]

On Wed, 27 Feb 2019 at 09:00, Vladimir Sitnikov
<si...@gmail.com> wrote:
>
> Hi,
>
> I see there's a bunch of tests written in Ant (see target
> name="batchtestserver" and target name="batchtest")
> It makes sense to rewrite the tests in Java / Groovy so the tests can
> be run individually, the output could be improved, timeouts could be

The tests can already be run individually.
Indeed that is part of the rationale for the targets.

> added, etc, etc.
>
> I don't really see the reason to use those Ant targets.

The batchtest target is used to run JMeter in batch mode using a
specific JMX file.
It needs to be run in its own JVM with its own I/O.

The batchtestserver target is for client-server tests, and needs to
run two separate JVMs.
These each need their own I/O as well.

Ant makes this possible to implement in a way that works across all OSes.

At the time, it was tricky to do this in Java, because it involves
interaction with the OS and shell.
I don't know if Java has improved since then.

> I see no reasons to migrate the targets to Gradle either.
>
> Any objections on that?

Provided that the tests can be written in a way that is
OS-independent, then no objection from me.

But I suspect this will be tricky to implement and harder to test properly.

Ant does it for free.

> Does anybody volunteer to rework those targets into a test class?
>
> Vladimir