db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Pendleton <bpendle...@amberpoint.com>
Subject Re: [jira] Updated: (DERBY-1417) Add new, lengthless overloads to the streaming api
Date Wed, 28 Jun 2006 14:15:18 GMT
Kristian Waagan (JIRA) wrote:
 > I will add tests, but have to wait until the signatures have made it into
 > Mustang (I do have some tests already, but here I use the specific
 > implementation classes, not the interfaces).

It seems to me that it's completely appropriate for tests to use
specific implementation classes. Why is that a problem?

Even if, in the longer run, we decide that the tests are more
elegantly implemented using the official interfaces, not the
underlying implementation classes, it seems to me it would be
good to have the less-than-perfect tests now, and replace them
later with superior tests, rather than having no tests at all.

Furthermore, it seems like the advantage of at least some level
of tests using the internal implementation classes, rather than the
official JDK 1.6 interfaces, is that such tests could be runnable
on JDK 1.4 and JDK 1.5 environments, meaning we'd have greater
coverage of a larger amount of our code.

Right now it scares me that there's this ever-increasing portion of
the Derby implementation that's just a complete unknown to me, stuck
as I am in my JDK 1.4/JDBC 3 world.



View raw message