John Embretsen wrote:
Hi Ramin,
Ramin Moazeni wrote:
Hi
I've been running derby tests (derbyall) before I can send out
a fix for review. In the report, I noticed that there are 13 suites
skipped
and no tests were run:
From the files you attached it looks to me as if the results you got
are as good as we could hope for :)
Not sure I understand.
What happened to the embedded tests and derbynetclientmats?
FYI, when I run derbyall now, I get around 314 tests (is being reduced
as people move/rewrite tests to JUnit) using Java SE 6 and including the
IBM driver. On my machine it takes around 1:45 -> 2+ hours.
Running with Java SE 5.0, I get around 307 tests (2 suites skipped).
I have not run without the IBM driver lately.
Last, just for information, derbyall is going to be gone in a "little
while". The main test suite will be suites.All, which is a JUnit suite.
regards,
--
Kristian
The derbynetmats tests/suites are skipped because you don't have
db2jcc.jar and db2jcc_license_c.jar in your classpath. These jars are
optional, for testing with the so-called "DerbyNet" framework (using
IBM's Universal JDBC driver), so this is OK.
The jdbc40 suite is skipped in all frameworks because you are running
the test with a version of Java that does not support JDBC 4.0. If you
run the tests using Java SE 6 (JDK 6), these tests will be run as well.
This is also optional, although the more tests you run the better.
