[
https://issues.apache.org/jira/browse/DERBY-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722006#comment-13722006
]
Bryan Pendleton commented on DERBY-6299:
----------------------------------------
Oh I see!
No, you don't need the "fail" directory at all. It is not part of the source
code, it is created by the running of Junit tests.
Does the "fail" directory go away if you run 'ant clean'? I think it should,
but maybe it doesn't.
If the 'fail' directory doesn't go away when you run 'ant clean', you can
just remove it.
But then we should probably log a separate issue to improve 'ant clean'
so that it cleans up this test directory.
In the meantime, I'll look at your latest patch, because it sounds like
it's getting close to what we want.
thanks,
bryan
> Improve the code coverage of Org.apache.derby.iapi.services.sanity package
> ----------------------------------------------------------------------------
>
> Key: DERBY-6299
> URL: https://issues.apache.org/jira/browse/DERBY-6299
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: ahsan shamsudeen
> Assignee: ahsan shamsudeen
> Priority: Minor
> Attachments: DERBY-6299.patch, DERBY-6299.patch
>
>
> According to the coverage reports, All classes in
> Org.apache.derby.iapi.services.sanity have completely zero coverage.
> So this sub-task is to improve code coverage by doing the following.
>
> 1)Change all the import statements in the code to reference the new location
> of SanityManager and
> AssertFailure
> 2) Delete the wrapper classes
> org.apache.derby.iapi.services.sanity.SanityManager
> org.apache.derby.iapi.services.sanity.AssertFailure
--
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