This bug names all classes in Core\Code\Rendering and, if existing, any corresponding test:
No direct unit test at all:
mitkBaseRenderer
mitkGeometry2DDataMapper2D
mitkGeometry2DDataVtkMapper3D
mitkGLMapper2D (small interface class, redesign possible?))
mitkGradientBackground
mitkManufacturerLogo
mitkMapper
mitkMapper2D (small interface class, redesign possible?)
mitkMapper3D (no code => no test needed)
mitkPointSetGLMapper2D
mitkPointSetVtkMapper3D
mitkPolyDataGLMapper2D
mitkRenderWindow
mitkRenderWindowBase
mitkRenderWindowFrame
mitkShaderRepository
mitkSurfaceGLMapper2D
mitkSurfaceVtkMapper3D
mitkVolumeDataVtkMapper3D
mitkVtkEventProvider
mitkVtkMapper2D (no code => no test needed)
mitkVtkMapper3D (refactoring is needed to fuse VTK 2D with 3D)
vtkMitkApplyLevelWindowToRGBFilter
vtkMitkRectangleProp
vtkMitkRenderProp
Tests which look extremely outdated and low coverage:
mitkVtkPropRenderer
Tests with rather medium coverage:
mitkVtkWidgetRendering (test seems okish, but what is the class used for?)
vtkMitkThickSlicesFilter
Different rendering tests with higher coverage exist for:
mitkImageVtkMapper2D
To sum up we have 30 classes and 4 interfaces-like classes. 4 classes of them have tests. 3 tests seem to need improvements. That means we need about 25 tests ;). Anyone is welcome to create a bug and a corresponding test for any of these classes.