[
https://issues.apache.org/jira/browse/DERBY-6307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750292#comment-13750292
]
Myrna van Lunteren commented on DERBY-6307:
-------------------------------------------
I agree that deferring testing of the javaDump() method is the right thing to
do.
To document my findings: I tried to capture the output, but it appears the
method causes the IBM JVMs to send a request to the OS, which 1. is possibly
different per OS and so gives possibly different results per OS, and 2. prints
out text that cannot be captured by System.out or System.err. Perhaps if we'd
call the method in a different process, but I think it all gets too complex for
the usage of the method.
The method is only used in two places (NetworkServerTestSetup, which I don't
think counts in the code coverage, and ContextManager, in the case of an error).
> Improve the code coverage of org.apache.derby.iapi.services.info.JVMInfo
> ------------------------------------------------------------------------
>
> Key: DERBY-6307
> URL: https://issues.apache.org/jira/browse/DERBY-6307
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: ahsan shamsudeen
> Assignee: ahsan shamsudeen
> Priority: Minor
> Fix For: 10.11.0.0
>
> Attachments: DERBY-6307.patch, DERBY-6307Temp.patch
>
>
> According to the coverage reports,
> org.apache.derby.iapi.services.info.JVMInfo is poorly exercised by the Derby
> regression tests.
> This sub-task is to improve that test coverage.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
