The streams package recently added tests for exercising package-private
implementation.
Top level dir contain the TEST.properties to add to the bootclasspath:
http://hg.openjdk.java.net/jdk8/tl/jdk/file/510035b7bbbb/test/java/util/stream/boottest/
Example, individual test, whose test is in the java.util.stream package:
http://hg.openjdk.java.net/jdk8/tl/jdk/file/510035b7bbbb/test/java/util/stream/boottest/java/util/stream/DoubleNodeTest.java
-Chris.
On 25/06/2013 01:51, huizhe wang wrote:
Thanks Sean and Rob.
Yes, I was told before to avoid shell scripts in tests. I'll wait till
after your investigation to see what's the best to do in this case.
-Joe
On 6/24/2013 3:42 PM, Rob McKenna wrote:
Some interesting conversations were had lately about shell scripts
during Joe Darcy's recent infrastructure tech talk. In particular
around the idea of a "jdk.testing" package to provide libraries that
would help with the types of operations seen in shell scripts. I'm
really hoping to spend some time on this myself over the coming weeks.
(in an effort to at least understand why we need shell scripts and
whether we could do something else instead)
In any case it should be possible to simply replace the script with a
java program that does the same thing. That would require fiddling
with Process however, and its debatable as to whether that would
result in fewer test failures. (shell scripts counting for a
proportionally large number of those failures) JSR199 might help to
reduce the amount of ProcessBuilders required in this instance.
-Rob
