Bug 550576 - [test] JavaCorePreferenceModifyListenerTest doesn't work as an AbstractJavaModelTest
Summary: [test] JavaCorePreferenceModifyListenerTest doesn't work as an AbstractJavaMo...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.13   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-29 15:20 EDT by Stephan Herrmann CLA
Modified: 2023-08-10 05:15 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Herrmann CLA 2019-08-29 15:20:36 EDT 
When running AllJavaModelTests in the IDE, we see an unparented test testPreApply(), which is contributed by JavaCorePreferenceModifyListenerTest.

I thought, the author simply forgot to integrate it properly with AbstractJavaModelTests and a proper suite() method, but when I tried that, AbstractJavaModelTests.tearDown() complains that settings are not at their default!

If that test indeed messes up JDT/Core preferences, it can cause much pain in subsequent tests.
Comment 1 Eclipse Genie CLA 2021-08-19 06:29:11 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2023-08-10 05:15:17 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.