RFR 8159126 Add test to validate DriverManager.println output whenDriverManager is initially loaded
lance.andersen at oracle.com
Mon Sep 12 19:56:11 UTC 2016
Thank you for the suggestions…
> On Sep 12, 2016, at 3:10 PM, ecki at zusammenkunft.net wrote:
> It looks like the test passes when the IOException happens (skips assert).
While I could add Assert.fail() catch blocks, I did not really see the need given this is in a controlled environment
> Besides, what about actually providing a well known driver (only?).
That makes the test heavier than it needs to be for this specific scenario and really do not need a driver to validate, including a stub driver
> Then you dont have to depend on the debug output.
The idea is to validate the println output is available and that specific message has been there for almost 20 years and no plans to change that anytime soon.
> From Win 10 Mobile
> Von: Lance Andersen
<http://oracle.com/us/design/oracle-email-sig-198324.gif>Lance Andersen| Principal Member of Technical Staff | +1.781.442.2037
Oracle Java Engineering
1 Network Drive
Burlington, MA 01803
Lance.Andersen at oracle.com <mailto:Lance.Andersen at oracle.com>
More information about the core-libs-dev