Re: Some JUnit tests now split out from old harness and do not run as part of derbyall

2006-10-20 Thread Dyre . Tjeldvoll
Vemund Ostgaard [EMAIL PROTECTED] writes: Daniel John Debrunner wrote: I would encourage those that regularly run nightly or other testing to add this JUnit test into their framework. I'm sure there will be some issues getting it running on all the platforms but they should be easy to work

Re: JUnit disagnostice (Was Re: Some JUnit tests now split out from old harness and do not run as part of derbyall)

2006-10-20 Thread Vemund Ostgaard
Daniel John Debrunner wrote: Vemund Ostgaard wrote: When running the top-level suite now, the only output I got was a lot of dots, the time it took to run the suite and the number of OK tests run. Have anyone considered a framework or interface for logging events and information in the

Re: JUnit disagnostice (Was Re: Some JUnit tests now split out from old harness and do not run as part of derbyall)

2006-10-20 Thread Sunitha Kambhampati
Daniel John Debrunner wrote: The Eclipse JUnit test runner is similar to the swing one but better. http://open.ncsu.edu/se/tutorials/junit/ It correctly shows which tests have run (the swing test runner seems to have bugs in it) and dynamically indicates which test is currently running. It

Re: JUnit disagnostice (Was Re: Some JUnit tests now split out from old harness and do not run as part of derbyall)

2006-10-20 Thread Daniel John Debrunner
Sunitha Kambhampati wrote: Daniel John Debrunner wrote: The Eclipse JUnit test runner is similar to the swing one but better. http://open.ncsu.edu/se/tutorials/junit/ It correctly shows which tests have run (the swing test runner seems to have bugs in it) and dynamically indicates which

Re: Some JUnit tests now split out from old harness and do not run as part of derbyall

2006-10-19 Thread Vemund Ostgaard
Daniel John Debrunner wrote: I would encourage those that regularly run nightly or other testing to add this JUnit test into their framework. I'm sure there will be some issues getting it running on all the platforms but they should be easy to work through. I'm extending the nightly

JUnit disagnostice (Was Re: Some JUnit tests now split out from old harness and do not run as part of derbyall)

2006-10-19 Thread Øystein Grøvlen
Vemund Ostgaard wrote: When running the top-level suite now, the only output I got was a lot of dots, the time it took to run the suite and the number of OK tests run. Have anyone considered a framework or interface for logging events and information in the junit tests? I think it will be

Re: JUnit disagnostice (Was Re: Some JUnit tests now split out from old harness and do not run as part of derbyall)

2006-10-19 Thread Daniel John Debrunner
Øystein Grøvlen wrote: Vemund Ostgaard wrote: When running the top-level suite now, the only output I got was a lot of dots, the time it took to run the suite and the number of OK tests run. Have anyone considered a framework or interface for logging events and information in the junit

Re: JUnit disagnostice (Was Re: Some JUnit tests now split out from old harness and do not run as part of derbyall)

2006-10-19 Thread Daniel John Debrunner
Daniel John Debrunner wrote: Øystein Grøvlen wrote: Vemund Ostgaard wrote: When running the top-level suite now, the only output I got was a lot of dots, the time it took to run the suite and the number of OK tests run. The Eclipse JUnit test runner is similar to the swing one but better.

Re: Some JUnit tests now split out from old harness and do not run as part of derbyall

2006-10-18 Thread Dyre . Tjeldvoll
Daniel John Debrunner [EMAIL PROTECTED] writes: As discussed and recorded in DERBY-1952 I have split some of the JUnit tests out so that they are *no longer* run under the old test harness and hence are *not* part of derbyall. (on the trunk). A top-level JUnit test (suite) exists that runs

Some JUnit tests now split out from old harness and do not run as part of derbyall

2006-10-17 Thread Daniel John Debrunner
As discussed and recorded in DERBY-1952 I have split some of the JUnit tests out so that they are *no longer* run under the old test harness and hence are *not* part of derbyall. (on the trunk). A top-level JUnit test (suite) exists that runs all the tests that were removed from derbyall, the