[Db-derby Wiki] Update of "DerbyJUnitTesting" by KristianWaagan

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by KristianWaagan:
http://wiki.apache.org/db-derby/DerbyJUnitTesting

The comment on the change is:
Removed section, serves no purpose and is not maintained.

------------------------------------------------------------------------------
  
  Click here on more information on the roadmap to [:KillDerbyTestHarness:completing the switch to JUnit].
  
- == Requested features for the JUnit harness ==
- Features requested for the JUnit harness on derby-dev. Note that this page is intended to be a summary page only. In general, all information presented here should be found in the mail archives for derby-dev as well (you can search here: http://www.nabble.com/Derby-f356.html).
- 
- '''Please add new items to the end so that the numbering of items is kept consistent.'''
- 
-  1. Central method to get connections, independent of test platform and framework.
-     http://www.nabble.com/forum/ViewPost.jtp?post=2587791
-  1. A way for tests to handle JVM specific, framework specific and version specific logic.
-     http://www.nabble.com/forum/ViewPost.jtp?post=2581937 (initial request)[[BR]]
-     http://www.nabble.com/forum/ViewPost.jtp?post=2732566 (more details)
-  1. A way to skip individual tests without causing errors, but with some informational message/logging.
-     http://www.nabble.com/forum/ViewPost.jtp?post=2732566
-  1. Mechanism for comparing runtimestatistics.
-     http://www.nabble.com/forum/ViewPost.jtp?post=2732566
-