UAST
TestCase with non-trivial constructors
Warning
New
Last modified: 03 December 2024 Reports test cases with initialization logic in their constructors. If a constructor fails, the @After
annotated or tearDown()
method won't be called. This can leave the test environment partially initialized, which can adversely affect other tests. Instead, initialization of test cases should be done in a setUp()
or @Before
annotated method.
Bad example:
public class ImportantTest {
private File file;
public ImportantTest() throws IOException {
file = File.createTempFile("xyz", ".tmp");
}
// ... tests go here
}
- By ID
Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.
JUnitTestCaseWithNonTrivialConstructors
Inspection Details | |
---|---|
By default bundled with: | |
Can be installed with plugin: | Java, 243.23126 |
Thanks for your feedback!
Was this page helpful?