Hi Martin,
>> BTW: Switching can be done nearly automatically via an eclipse plugin:
>> http://testng.org/doc/migrating.html
>
> That would probably be useful for a large amount of tests. But
> GeoAPI-conformance makes extensive use of parametrized tests (since
> the implementation must be specified) and listeners; I would be
> impressed if the plugin was sophisticated enough for converting such
> tests automatically.
ok, I understand
>>> The capability to specify tests dependencies seems attractive
>> you can do so for junit too or what do you mean here?
>
> JUnit provides TestSuite, but I was hopping for a simpler annotation
> like:
>
> class TestA {...}
>
> @Depends(TestA.class)
> class TestB {...}
ah, I see. I don't think there is something similar (only a limited
functionality via subclassing tests)
>>> , and the fact that TestNG doesn't recreate new "FooTest" instance for
>>> every tests may speed-up when the constructor performs heavy
>>> initialization.
>> Constructors shouldn't do that ;)
>
> I should have mentioned methods annotated by @Before instead. JUnit
> has @BeforeClass for initializing resources only once, but it force us
> to store the resources in static fields, which may cause the JVM to
> retain them longer then needed (while I admit we can set the static
> fields to null explicitly in an @AfterClass method).
Yes, static is ugly. Also one wouldn't be able to parallelize the tests
at some point in the future
... now I'm unsure what to choose ;) !
Regards,
Peter.
