Hi,
Issues/concerns about breakage/compatibility:
- JUnit3 tests can be run with the JUnit4 and JUnit3 test runner
(launch configuration).
- JUnit4 tests can not be run with JUnit3!
- tests that have been built with RienaTestCase and/or use the
TestCollector still run both with the JUnit3 and JUnit4 test runner
- our annotations for the TestCollector will still be used.
However, the TestCollector will get a ´colleague´ i.e. TestCollector4
which fits with JUnit4. Additionally there is a JUni4TestsRunner (which
I wrote) that bridges the loss of the no longer supported "static Test
suite()" methods.
- yep, would be really nice if the tests run on the build server -
volunteers one pace forwards!
- having a special bundle (or better two) that contains our test
specific extensions?
Yes! Good point!
- a CQ? Probably, but that should be no problem. JUnit4 is already
in the orbit.
Tschüß,
Stefan
On 27.03.2010 01:59, Christian Campo wrote:
While I think in general its a good idea, I am concerned about breakage:
- tests that we have that run under 3.8 if they all run with junit 4
- tests that others have built on top of RienaTestCase, will they continue to run
- and a thing that Elias brings up is equally im important. we need to make sure that the test continue to run
I also suggest that we start with factoring out the test support stuff that I believe is currently in riena.core to a new bundle riena.testutils or something
where we keep the RienaTestCase and the Annotations that support it.
What will happen to the Annotation that we currently use ? Will they be supported in Junit4 or will they be replaced by new mechanism ?
Does it make sense to create riena.testutil3 and riena.testutil4 bundles for the different junit test libs ?
And I believe e we need an CQ which I can do.
christian
Am 26.03.2010 um 11:21 schrieb Elias Volanakis:
IMHO the first thing to check is how we can run junit4 tests on the
build server.
Once we know this works I'm ok with switching.
Kind regards,
Elias.
On Thu, Mar 25, 2010 at 7:10 AM, Stefan Liebig
<Stefan.Liebig@xxxxxxxxxxxx> wrote:
Hi Rienars,
I would like to do a poll for switching - sometime - to the latest version
of JUnit (4.8.1) - already in the orbit
A few points to mention (both good and "bad"):
JUnit4 is supported by the Eclipse IDE ==>
http://wiki.eclipse.org/Eclipse/Testing/JUnit4_Changes
uses annotations instead of conventions - some really nice gems here, e.g.
the @Ignore annotation. Tests marked with that will not be executed but got
listed as ignored (they will not forgotten!)
there is no longer support for the "static Test suite()" method which we use
with our TestCollector :-(
However, I have created a special "Runner" that bridges this gap :-)
Riena users using RienaTestCase and TestCollector should not be affected
probably changes to our build "scripts" (Hudson, ..)
Thoughts + comments?
Tschüß,
Stefan
-------------------------------------------------------------
compeople AG
Untermainanlage 8
60329 Frankfurt/Main
fon: 069 / 27 22 18 0
fax: 069 / 27 22 18 22
web: www.compeople.de
Vorstand: Jürgen Wiesmaier
Aufsichtsratsvorsitzender: Christian Glanz
Sitz der Gesellschaft: Frankfurt/Main
Handelsregister Frankfurt HRB 56759
Ust-Ident.-Nr: DE207665352
-------------------------------------------------------------
_______________________________________________
riena-dev mailing list
riena-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/riena-dev
--
Elias Volanakis | Technical Lead | http://eclipsesource.com
elias@xxxxxxxxxxxxxxxxx | +1 503 929 5537 | @evolanakis
_______________________________________________
riena-dev mailing list
riena-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/riena-dev
_______________________________________________
riena-dev mailing list
riena-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/riena-dev
|