The class junit.extensions.TestSetup changes the
behavior of setUp and tearDown. Under TestSetup,
setUp and tearDown are called once for all test
methods, instead of once for each test method.
Since JFCTestCase is a subclass of TestCase, it can
not behave like TestSetup. In writting JFC tests, a
person may want to call setUp and tearDown only once.
Possible Solutions:
A - Maybe we introduce new methods (setUpOnce,
tearDownOnce)
B - Get JUnit to change to provide hooks to control
how JFCTestCase is called.
C - Create JFCTestSetup (subclass of TestSetup
instead of TestCase)
D - ??
Logged In: YES
user_id=327012
From what I saw - with the previous version - if we
initialized JFCTestHelper just once (since it is usually
done inside the setUp method), it actually broke the tests
since the handles to the windows was not refreshed.
But with the new JFCTestEventListener - maybe this would
work.
I am not sure yet.
Logged In: YES
user_id=327012
From what I saw - with the previous version - if we
initialized JFCTestHelper just once (since it is usually
done inside the setUp method), it actually broke the tests
since the handles to the windows was not refreshed.
But with the new JFCTestEventListener - maybe this would
work.
I am not sure yet.