DO NOT EDIT OR ANSWER THIS ISSUE. SEE THE ORIGINAL ISSUE INSTEAD:
ORIGINAL REPORTER: alex
After the refactoring of the JFireTestSuite the subclasses of
org.nightlabs.jfire.testsuite.TestSuite are not used any more.
However these classes had two main functions:
1. They grouped TestCases. This was not done actively, instead the
grouped TestCases referenced a TestSuite as @JFireTestSuite.
2. They had the canRunTests-method that checked whether the
prerequisites were fulfilled in order to run the tests of the suite
Both functions should be reactivated in the new TestCase-Structure.
Ideas for the implementation in the current situation are:
1. Grouping the tests should be done using the new JUnit4-way. The
Suites should all be annotated with the
@RunWith(Suite.class)-annotation and reference those classes in
the @SuiteClasses-annotation that formally referenced the
TestSuite as JFireTestSuite. I've already done that as reference
Additionally these suites should be
grouped into two main suites - one for JFireMin one for
JFireMax. Each one with its own project. JFireTestSuiteMax is
already started, but currently references the TestClasses
directly instead of the JFireMin-suite and all additional suites
2. Skipping test when prerequisites are not fulfilled, or better
assuring that those prerequisites are fulfilled (What was
formally done in the canRunTest-method): Unfortunately I'm not
aware of a method to do that with JUnit directly. Ideas to check
* Check whether there is a standard-method in JUnit3 (this
is what all tests use)
* See if the API of TestCase (the JFire-subclass) can be
extended in order to check prerequisites (like for example
setupBeforeClass). Problem here is that if the run is
simply not executed, the run-notifier still has to be
notified in order for the listener to report that to the
UI and continue with the next test in the suite.
Log in to post a comment.