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
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
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
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
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
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
Ø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
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.
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
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
10 matches
Mail list logo