Issue Details (XML | Word | Printable)

Key: JDBC-201
Type: Task Task
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Mark Rotteveel
Reporter: Mark Rotteveel
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Jaybird JCA/JDBC Driver

Migrate JUnit tests to JUnit 4

Created: 20/Nov/11 03:04 PM   Updated: 07/May/17 12:32 PM
Component/s: None
Affects Version/s: None
Fix Version/s: Jaybird 3.0.0


 Description  « Hide
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).

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Mark Rotteveel added a comment - 14/Jul/12 03:15 PM
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).

Mark Rotteveel added a comment - 05/Aug/12 06:16 PM
Changed prio to critical as doing this early so new tests can take advantage of JUnit 4 features.

Mark Rotteveel added a comment - 06/Aug/12 01:03 PM
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.

Mark Rotteveel added a comment - 06/Aug/12 01:10 PM
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.