On Fri, 2004-06-11 at 11:51, Rodney Waldhoff wrote:
> On Fri, 11 Jun 2004, Alex Karasulu wrote:
>
> > I looked at JUX just now and saw that you have one class there called
> > ObjectTestCase.java. Would you rather move the stuff already put into
> > test to JUX or just add this class to the test
On Fri, 11 Jun 2004, Alex Karasulu wrote:
I looked at JUX just now and saw that you have one class there called
ObjectTestCase.java. Would you rather move the stuff already put into
test to JUX or just add this class to the test project?
Feel free to move it (and its tests) over to the test projec
> contrary to as someone pointed out on this thread I think this subject
> is very exciting. For my development projects I have also founded a
Sorry man I did not mean to insult those who are religious about testing
when I said it was boring. It's just not my favorite topic although I
do enjoy
On Fri, 2004-06-11 at 08:51, Zeigermann, Oliver wrote:
> I have created a concurrent package under o.a.c.test. I guess "Threading" and
> "Futures" might fit there perfectly...
That's great! I only had the chance to add a dinky lil class or two but
will add more as time progresses.
Alex
---
On Fri, 2004-06-11 at 08:53, Rodney Waldhoff wrote:
> On Wed, 9 Jun 2004, Alex Karasulu wrote:
>
> > 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
On Wed, 9 Jun 2004, Alex Karasulu wrote:
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 ar
[testutils] Is there any commons area for generic test code?
Alex Karasulu wrote:
>
> Back on topic, I'm fine with guidelines. But I only have general ones at
> the moment:
>
> o I want to minimize dependencies avoiding them whenever possible.
> o Keep things s
Alex Karasulu wrote:
>
> Back on topic, I'm fine with guidelines. But I only have general ones at
> the moment:
>
> o I want to minimize dependencies avoiding them whenever possible.
> o Keep things simple.
> o This should not be an area for dumping project test code.
> o Keep the amount of spe
Alex Karasulu wrote:
On Thu, 2004-06-10 at 21:39, Pete Gieser wrote:
I may have missed it, but I wanted to mention that there exists
a sourceforge project that may have some overlap.
http://sourceforge.net/projects/junit-addons
FWIW.
Pete
This is good stuff and pretty much in line with
On Thu, 2004-06-10 at 16:06, Martin van den Bemt wrote:
> We probably should check for some overlap.
> I have some Exception test stuff that could also come in handy.
> It allows you to test classloader exceptions (except NoClassDefFound,
> still have to figure that one out..). To get it into comm
We probably should check for some overlap.
I have some Exception test stuff that could also come in handy.
It allows you to test classloader exceptions (except NoClassDefFound,
still have to figure that one out..). To get it into commons I need to
make it more usable for others except myself howev
I may have missed it, but I wanted to mention that there exists
a sourceforge project that may have some overlap.
http://sourceforge.net/projects/junit-addons
FWIW.
Pete
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addition
> AK> I'll kick start a little sandbox project for common test related code
> AK> shared across ASF projects.
> AK>
> AK> What shall we call it? I figure 'test' is short and to the point.
>
> Yes. But I believe we must setup some kind of guide line, what we try to
> include and what not. E.g. I
On Thursday 10 June 2004 16:18, Alex Karasulu wrote:
AK> On Thu, 2004-06-10 at 05:28, Jörg Schaible wrote:
AK> > Hi Alex,
AK> >
AK> > in our project I have meanwhile also a collection of utility classes,
that I AK> > use over again in unit tests. It might be good to have a more
common pool. AK>
.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] I
Right, I will add my stuff at random as well...
Oliver
Alex Karasulu wrote:
On Thu, 2004-06-10 at 11:36, Oliver Zeigermann wrote:
Nice, will do so ASAP. Any idea how to structure all this?
The only structure I have in mind right now is the o.a.c.test package
:-). Perhaps as we fill it with matter
On Thu, 2004-06-10 at 11:48, Oliver Zeigermann wrote:
> Alex Karasulu wrote:
>
> > On Thu, 2004-06-10 at 10:29, Oliver Zeigermann wrote:
> >
> >>I could contribute a class called RendezvousBarrier. It is simple, but
> >>very useful when testing stuff in concurrent szenarios and you want to
> >>
Alex Karasulu wrote:
On Thu, 2004-06-10 at 10:29, Oliver Zeigermann wrote:
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 t
On Thu, 2004-06-10 at 11:36, Oliver Zeigermann wrote:
> Nice, will do so ASAP. Any idea how to structure all this?
The only structure I have in mind right now is the o.a.c.test package
:-). Perhaps as we fill it with matter we'll start to see more of a
structure naturally emerge.
I got me one
Nice, will do so ASAP. Any idea how to structure all this?
Oliver
Alex Karasulu wrote:
Olivier, JÃrg, Michael,
Sure this is just what we need I think. Let me get it setup and
mavenize it and we can just start adding our test code and organizing
it. I'll get on it right now.
Ok its done - you
Olivier, JÃrg, Michael,
> Sure this is just what we need I think. Let me get it setup and
> mavenize it and we can just start adding our test code and organizing
> it. I'll get on it right now.
Ok its done - you can checkout or update the jakarata-commons-sandbox
and a new test directory shoul
On Thu, 2004-06-10 at 05:28, JÃrg Schaible wrote:
> Hi Alex,
>
> in our project I have meanwhile also a collection of utility classes, that I
> use over again in unit tests. It might be good to have a more common pool.
Great news JÃrg! You put us over the top wrt my personal quota of 3
intereste
Hi Alex,
in our project I have meanwhile also a collection of utility classes, that I
use over again in unit tests. It might be good to have a more common pool.
This might be also a candidate:
http://issues.apache.org/bugzilla/show_bug.cgi?id=27663
-- Jörg
-
[snip]
> Just a thought - It might be interesting to look at the possibility of
> auto-generating testcode from the annotation features of Java 1.5. Take
> a look at these for some ideas:
>
> http://www.langrsoft.com/articles/annotations2.html
> http://www.onjava.com/pub/a/onjava/2004/04/21/dec
Alex Karasulu wrote:
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?
The problem with a project like this is that the scope would be hard to
define. The only
common thing that I use
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 extensio
26 matches
Mail list logo
