Details
-
Test
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
Unknown
Description
If you have test classes that does not directly extend CamelTestSupport then your tests may not cleanup after testing. All the tearDown is not invoked.
It seems its due to CamelTestSupport implements both some interfaces from JUnit and also have @AfterEach annotation and this skrews up junit when you have test class hierachies.
Attachments
Issue Links
- links to