[
https://issues.apache.org/jira/browse/IGNITE-12737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17052584#comment-17052584
]
Ivan Pavlukhin commented on IGNITE-12737:
-----------------------------------------
[~zzzadruga], some historical note. The test class was added in a suite as
disabled in IGNITE-7615 when it was found belonging to no suite. Invalid
`@Test` annotation was added later during migration to junit4.
But generally I think it would be great to fix and enable the test in CI.
> Incorrect annotation on TxDeadlockCauseTest
> -------------------------------------------
>
> Key: IGNITE-12737
> URL: https://issues.apache.org/jira/browse/IGNITE-12737
> Project: Ignite
> Issue Type: Bug
> Reporter: Nikolai Kulagin
> Priority: Minor
>
> Method TxDeadlockCauseTest#testCauseObject() have annotation
> {color:#ffab00}@Test{color}, but it is not a test case. As a result, JUnit
> can run no one test in this class and printed error.
> {code:java}
> java.lang.Exception: Method testCauseObject should have no parameters.{code}
> Most likely TxDeadlockCauseTest.class was commented on in the suite
> TxDeadlockDetectionTestSuite because of this.
> I suggest:
> 1. Delete the annotation {color:#ffab00}@Test{color};
> 2. Fix the tests in TxDeadlockCauseTest (3 tests look good, 1 test fails);
> 3. Uncomment the TxDeadlockCauseTest in the suite.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
