When a test does not even get off of the ground, it sometimes does not output out any results, and therefore the test result formatter does not know about the test. That is why the number of tests sometimes varies.
Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., the leading provider of Net business solutions http://www.novell.com >>> [EMAIL PROTECTED] 6/14/02 7:50:35 AM >>> I ran the tests as per the instructions on http://lubega.com however my invocation of build run-basic-testsuite only generated 658 tests, with 228 successful, 418 errors, and 12 failures. I did a CVS update right after I got Chris's message. What am I doing wrong? That is a lot of errors. I am using the JDK1.4.0_01, and I noticed he was testing with JDK1.3.1 for that test. Different JDKs and platforms generated different numbers of tests and errors. Is there an explanation of why and what tests kick in for what platforms? Should I switch back to JDK1.3? Does the JDK1.4 always generate that many errors? Thanks. Fred. At 09:44 PM 6/13/2002, [EMAIL PROTECTED] wrote: >Number of tests run: 772 >-------------------------------------------- >Successful tests: 763 >Errors: 6 >Failures: 3 _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
