New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate JUnit tests to JUnit 4 [JDBC201] #250
Comments
Commented by: @mrotteveel For Jaybird 2.3 switch to JUnit 4, but only upgrade tests to JUnit 4 where needed (JUnit 3 tests should run without trouble under JUnit 4). |
Modified by: @mrotteveelFix Version: Jaybird 2.3 [ 10440 ] |
Commented by: @mrotteveel Changed prio to critical as doing this early so new tests can take advantage of JUnit 4 features. |
Modified by: @mrotteveelpriority: Minor [ 4 ] => Critical [ 2 ] assignee: Roman Rokytskyy [ rrokytskyy ] => Mark Rotteveel [ avalanche1979 ] |
Commented by: @mrotteveel Refactored SimpleFBTestBase to FBTestProperties, no longer inheriting from TestCase, moved a large number of test property related methods and factory methods from FBTestBase to FBTestProperties. Moved several helper methods for test DDL and closing JDBC resources to separate helper classes. Introduced FBJUnit4TestBase with similar setup as FBTestBase and converted TestFBSavePoint to a JUnit 4 test. |
Commented by: @mrotteveel From now on, tests should be written in JUnit 4, but I didn't mark FBTestBase as deprecated to prevent a hundred annoying deprecation warnings. Moving existing tests over to JUnit 4 will only happen if it is either necessary or if the test-class is undergoing major changes. |
Modified by: @mrotteveelstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @mrotteveel
Migrate the existing tests from JUnit 3 to JUnit 4, and use the new features to have tighter control on the tests executed or skipped (instead of using a list in build/test.xml).
Commits: 358e024 4a752bd 2470f11 5b74070
The text was updated successfully, but these errors were encountered: