On Thu, Oct 24, 2013 at 1:45 AM, Benedikt Ritter <[email protected]>wrote:
> > > Send from my mobile device > > > Am 23.10.2013 um 16:12 schrieb Stefan Bodewig <[email protected]>: > > > >> On 2013-10-23, Gary Gregory wrote: > >> > >> Consider using JUnit's Assume to skip testing, this will allow IDEs and > >> tools to know a test has been skipped. > > > > Unfortunately the test like many of Compress' tests is in JUnit 3.x land > > - something to change if we ever get 2.x off the ground. > > I don't see a reason to wait for 2.x before updating to JUnit 4. The old > tests will be executable without changes. > Am I missing something here? > Updating to JUnit 4 from 3 is not always a drop in replacement. I've run into cases that required tweaking. G > > Benedikt > > > > > Stefan > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- E-Mail: [email protected] | [email protected] Java Persistence with Hibernate, Second Edition<http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
