Given a legacy application with lots of tests it may be assumed the EDT is violated multiple times.
It is then not easily possible to write new functionality with tests that treat the EDT well. Because such tests would install the FailOnThreadViolationRepaintManager and since it won't be removed again, it remains active even for the legacy tests that may run afterwards.
So if you cannot control the order of your tests then it should be possible to remove an installed FailOnThreadViolationRepaintManager again.
Given a legacy application with lots of tests it may be assumed the EDT is violated multiple times.
It is then not easily possible to write new functionality with tests that treat the EDT well. Because such tests would install the
FailOnThreadViolationRepaintManager
and since it won't be removed again, it remains active even for the legacy tests that may run afterwards.So if you cannot control the order of your tests then it should be possible to remove an installed
FailOnThreadViolationRepaintManager
again.