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 failing tests in JUnit form) in attachment, and am wondering could you please have a look at that, to check whether they are real bugs or not? The 10 tests presented in the attachments violates one of the common Java code practices (at least in my viewpoint): if all the inputs are not null, there should not be null pointer exception thrown. The Junit tests attached are fully automatically generated, thus, the readability might not be so good. sorry... But they are generally relatively short. Thanks very much for your time! And any suggestion to the generated tests (including format and other aspects) are welcome! Best -Sai
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
