Tagir Valeev dcacf7ad56 [testFramework] Fix property tests ...

1. Do not set up default module for univocity project. The module exists already, and when we set up another one, crazy things start to happen. In particular, AbstractApplyAndRevertTestCase.initCompiler creates CompilerTester with random module (likely depending on previous tests), and if it happens to be the newly-created one, the CompilerTester don't set SDK to the 'main' module which causes later failure when compilation is attempted.
2. Do not try to dispose internalJDK twice. We add internal JDK inside BaseUnivocityTest.setUp (with disposable) and add it again inside CompilerTestUtil.enableExternalCompiler (with dispose at disableExternalCompiler). The one-arg addJdk() method doesn't check anything, so we actually add it twice. The removeJdk() method was also called twice which resulted in double disposal.

GitOrigin-RevId: d4e239047859ccb9602b17f512984c2ac83782c2

2022-11-03 21:09:53 +00:00

..

src/com

[testFramework] Fix property tests

2022-11-03 21:09:53 +00:00

intellij.java.testFramework.iml

[tests] make file comparison failure available in testFramework

2022-08-18 12:59:59 +00:00