[GEODE-217] Update DUnit framework to JUnit 4

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.0-incubating.M3
• Component/s: tests
• Assignee: Kirk Lund
• Reporter: Kirk Lund
• Created: 13/Aug/15 18:51
• Updated: 22/Aug/16 16:54
• Resolved: 15/Jun/16 16:07

Description

DUnit tests are currently limited to JUnit 3.8 syntax and functionality. Geode developers would like to be able to use JUnit 4.0 syntax and functionality including Rules.

Given the large number of DUnit tests it's probably more feasible to introduce a new DUnit framework in package com.gemstone.gemfire.test.dunit in the gemfire-core project. Then DUnit tests can be migrated one at a time from using the old implementation in package dunit.* to using the new one.

Sub-Tasks

• Add @DistributedTest to DistributedTestCase: Closed
• Move dunit.standalone to com.gemstone.gemfire.test.dunit.standalone: Closed
• Add custom annotations and rules for distributed tests: Closed
• Move dunit to com.gemstone.gemfire.test.dunit: Closed
• Extract static methods from DistributedTestCase: Closed
• Refactor DistributedTestCase tearDown to use template methods: Closed
• Define JUnit 4 versions of DistributedTestCase and CacheTestCase: Closed
• Define new DistributedTestRule to replace DistributedTestCase: Closed
• Define new CacheTestRule to replace CacheTestCase: Closed
• Refactor FieldSerializationUtils to improve local variable names: Closed
• CacheTestCase should default to JUnit4CacheTestCase: Closed