Hello Julius,
This is a thing we need, but I think you should change the issue name,
which is not really in sync with the description.
It says "will access a private fields of derby classes". Accessing
private fields is a whole different story, and is most definitely
something we don't want to do.
You do mean package-private classes, right?
This will allow us to invoke all methods except private methods in these
classes. The same goes for fields.
thanks,
--
Kristian
Julius Stroffek (JIRA) wrote:
Create a framework for writing unit tests that will access a private fields of
derby classes.
---------------------------------------------------------------------------------------------
Key: DERBY-2460
URL: https://issues.apache.org/jira/browse/DERBY-2460
Project: Derby
Issue Type: New Feature
Affects Versions: 10.3.0.0
Reporter: Julius Stroffek
Priority: Minor
Create a testing framework for writing unit tests that will not test the
functionality but some other properties of the code like DRDA protocol,
conditions of B-trees, behavior of locking, etc. These tests may be written in
a same way like the function tests are but they will not test the public API
but some underlaying Derby functions. So, there is a need for the tests to
access some package private properties/methods.
The discussion about this issue took place on derby-dev couple of months ago.
Please, see
http://www.nabble.com/Testing-implementation-of-private-classes-tf2919330.html#a8158779
for more information.
Currently, there is an implementation of such a test in
org.apache.derby.impl.drda.TestProto.
