[
https://issues.apache.org/jira/browse/DERBY-5301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092345#comment-13092345
]
Knut Anders Hatlen commented on DERBY-5301:
-------------------------------------------
> It took me a while to figure this out because when this happens, the test
> case gets an assertion about
> the table-level locking problem, but then the tearDown() method gets another
> assertion, and that exception
> hides the test problem.
I think this is something that was fixed in JUnit 3.8.2, so that newer versions
don't let failures in tearDown() hide failures in the test methods. In case
you're still using JUnit 3.8.1 to run the tests.
> Convert store/TableLockBasic.sql to junit
> ------------------------------------------
>
> Key: DERBY-5301
> URL: https://issues.apache.org/jira/browse/DERBY-5301
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: Houx Zhang
> Assignee: Houx Zhang
> Labels: gsoc2011
> Attachments: 5301-1-part.patch, TableLockBasicTest.java, junit.out
>
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
