I agree, adding functionality tests for the samples would be very nice, though probably a lot of work since they only make sense when going through real-world scenarios and not just hitting a single action repeatedly. A nice task to keep in the back of our minds for when we ever hit a moment of boredom ;-)
On 23 Aug 2007, at 19:55, Juris Galang wrote: > We should be able to get rid of that. But it'd be nice to add/ > feature unit tests in our demos as well. > > On Aug 23, 2007, at 2:37 AM, Geert Bevin wrote: > >> Hi, >> >> for a while I've been closing the coordination demo project in >> Eclipse since it always gave me errors. Today I took a look at it and >> it seems that this file is the culprit: code/demos/pojo/coordination/ >> test/ConfigTest.java >> >> It references a lot of classes that are nowhere to be found, not even >> when searching through Fisheye, like >> com.tc.newconfig.source.ConfigSource. >> >> Does anyone know what is supposed to happen with this. It feels like >> an unmaintained file from some ancient revision that could be >> removed. Thoughts? >> >> Thanks, >> >> Geert >> >> -- >> Geert Bevin >> Terracotta - http://www.terracotta.org >> Uwyn "Use what you need" - http://uwyn.com >> RIFE Java application framework - http://rifers.org >> Music and words - http://gbevin.com >> >> _______________________________________________ >> tc-dev mailing list >> [email protected] >> http://lists.terracotta.org/mailman/listinfo/tc-dev > -- Geert Bevin Terracotta - http://www.terracotta.org Uwyn "Use what you need" - http://uwyn.com RIFE Java application framework - http://rifers.org Music and words - http://gbevin.com _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
