Please check if the PR fulfills these requirements
[x] The commit message follows our guidelines
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
In the TextNodeTest class, the custom getLabelProvider function, defined in the TextNodeTest class returns the labelProvider variable if this variable is not null or a customized LabelProvider if the labelProvider variable is null :
In the TextNodeTest > testSubstationDescriptiontest, the labelProvider variable was instantiated with a new DefaultLabelProvider(...) and thus not null.
Because of that, the customized LabelProvider, with its customized getVoltageLevelDetails method is not used.
It seems like it should be, in order to test the setVoltageLevelDetails(true) configuration.
What is the new behavior (if this is a feature change)?
The instantiation of the labelProvider variable is removed so that the customized LabelProvider is used.
The test resource file is modified (voltage level details now appear in the text box).
Does this PR introduce a breaking change or deprecate an API?
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? Bug fix
What is the current behavior? In the
TextNodeTest
class, the customgetLabelProvider
function, defined in theTextNodeTest
class returns thelabelProvider
variable if this variable is notnull
or a customizedLabelProvider
if thelabelProvider
variable is null :In the
TextNodeTest
>testSubstationDescription
test, thelabelProvider
variable was instantiated with anew DefaultLabelProvider(...)
and thus notnull
.Because of that, the customized
LabelProvider
, with its customizedgetVoltageLevelDetails
method is not used. It seems like it should be, in order to test thesetVoltageLevelDetails(true)
configuration.What is the new behavior (if this is a feature change)? The instantiation of the
labelProvider
variable is removed so that the customizedLabelProvider
is used. The test resource file is modified (voltage level details now appear in the text box).Does this PR introduce a breaking change or deprecate an API?