Re: Potential bugs in commons 3.2 with JUnit tests

2010-08-17 Thread Sai Zhang
Hi Ted: Thanks for your reply. The first 5 failing test is due to a null value in the top level (when constructing the object), though not in the argument place. The test case generated by the tool reveals a corner case like: Closure var0 = null; Closure[] var1 = new Closure[]{var0}; ChainedClo

Re: Potential bugs in commons 3.2 with JUnit tests

2010-08-17 Thread Sai Zhang
you put the reports onto a web-site? > > On Tue, Aug 17, 2010 at 12:04 PM, Sai Zhang >wrote: > > > Hi all: > > > > I am now writing an automated test generation tool for Java, and use > Apache > > Common Collections > > version 3.2 (latest release) as one

Potential bugs in commons 3.2 with JUnit tests

2010-08-17 Thread Sai Zhang
Hi all: I am now writing an automated test generation tool for Java, and use Apache Common Collections version 3.2 (latest release) as one of the experimental benchmarks. According to the tool design and its internal checking mechanism, it generates many failing tests. I attach 10 (executable fa