'Threads outliving test methods in JUnit and interferes with other test methods
I have a method that launches a thread which I have no control over. I do not have a mechanism to stop it. I however expected for the thread launched in the test method to be killed when the test method execution is over. But this is not the case, I could see logs from the earlier test method in the current test method in execution. Is there a setting or anything I could do to ensure that all threads after a test is cleaned up?
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|