There is a class called Rendezvous in Mr. Lea's code. I assumed that's what you're attempting.
-----Original Message----- From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] Sent: Thursday, June 10, 2004 10:52 AM To: Jakarta Commons Developers List Subject: Re: [testutils] Is there any commons area for generic test code? I suppose you refer to CyclicBarrier, right? Actually, RendezvousBarrier is heaviliy "inspired" by this one, but addionally allows to increase the barries without the current thread being forced to wait for the others. Maybe it would have been possible to use the one from Douge Lea anyway, but is it worth including the whole package? Cheers, Oliver James Carman wrote: > That sort of code (the rendezvous) is going to be included in the 1.5 > release of Java. In the meantime, it's included in a code library > http://gee.cs.oswego.edu/dl/cpj/) by Doug Lea who wrote Concurrent > Programming in Java. > > -----Original Message----- > From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 10, 2004 10:29 AM > To: Jakarta Commons Developers List > Subject: Re: [testutils] Is there any commons area for generic test code? > > I could contribute a class called RendezvousBarrier. It is simple, but > very useful when testing stuff in concurrent szenarios and you want to > make non-deterministic runs of more than one thread deterministic for > certain tests. > > Additionally, I have a set of methods that do comparison on files. They > include checking the content of text files as well as checking what > files are in certain directories. > > A few other methods as well. > > If of any interest I could offer to contribute and maintain all of them > in a testutils component... > > Oliver > > Alex Karasulu wrote: > > >>Hi, >> >>I've often found it necessary to write some of the same test code >>snippets over and over again. Namely I'm referring to test cases for >>private methods that use reflection as well as other common snippets of >>code dealing with unit tests. Some of these snippets could have become >>JUnit extensions. >> >>Is there a place where we can collect and localize utility methods and >>classes used for unit testing? I have not found anything yet. >> >>Is it even worth doing this? >> >>If the answer is "no", then "yes" to the two questions above, is it >>worth creating a sandbox area where we can start gathering useful >>utilities for unit testing? >> >>IMO most projects could benefit from unit testing utilities or >>extensions that do not come out of the box with JUnit or mock objects. >>Personally I'm looking for a place where I can keep generic test code >>that could be used across projects, while sharing testing strategies and >>techniques with others. Sometimes nothing better communicates ideas >>than actual code. So if nothing already exists perhaps we can use this >>area as a place to gather modest utilities; very simple tools. It can >>grow as demands increase and need not be a full fledged production: >>meaning there is no rush or stress to make it into a release or a >>deliverable. >> >>Also perhaps things like the commons collections testing framework could >>be kept here as well. Don't if this is the right thing to do but just a >>thought. It might not be a good idea since it is so specific to >>collections but this can be discussed over time. >> >>Why this email now? >> >>I sat down this morning to write a few JUnit tests and realized I needed >>to write the same darn utility code over again for common issues I deal >>with while testing. That's what triggered this email. 9 out of 10 >>times I can find existing JUnit AddOns that help but sometimes they need >>to be altered or augmented in some respect. Rather then impose >>dependencies where I cannot make additions to the code I thought it >>would be nice if we had our own test utilities where additions can be >>made on demand. I thought for sure others had this wish at some point. >> >>WDYT? >> >>Alex >> >> >> >> >>--------------------------------------------------------------------- >>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] > > > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
