Summary of bug description

• actual behaviour

some property classes have a defective == operator. They compare if the pointer to their data objects are equal, not if the data objects themselves are equal

• expected behaviour they should compare the data objects, not the pointers.

Cause of the bug

• wrong implementation from the start, no unit test caught this, no one probably used the == operators before

Proposed solution

• compare the data objects, add == operator to the data objects if necessary.

Affected classes

• mitkLookupTableProperty.cpp --> compare data objects

• mitkTransferFunction.cpp + .h --> add == operator

• mitkTransferFunctionProperty.h --> compare data objects

How will the bugfix get tested?

• mitkSceneSerializationTest.cpp uses the == operator of all properties.