diff --git a/Documentation/Doxygen/DeveloperManual/HowTos/InteractionTestingHowTo.dox b/Documentation/Doxygen/DeveloperManual/HowTos/InteractionTestingHowTo.dox
new file mode 100644
index 0000000000..88bb0874e7
--- /dev/null
+++ b/Documentation/Doxygen/DeveloperManual/HowTos/InteractionTestingHowTo.dox
@@ -0,0 +1,70 @@
+/**
+
+\page InteractionTestingHowTo Interaction Testing in MITK
+
+\tableofcontents
+
+\section RecordingInteractions Recording Interactions
+To be able to record interactions activate Interaction Event Recorder in MITK-build cmake.
+The following table explains how to step-wise create an interaction sequence, which is necessary for developing interaction tests.
+The given example shows how the AddTool Segmentation Interaction Test was developed.
+For implementation examples refer to mitkToolInteractionTest.cpp or mitkPlanarFigureInteractionTest.cpp
+
+Step           | AddTool Segmentation Example
+-------------- | ----------------------
+Load Image | MITK-Data/Pic3D.nrrd
+Do not scroll image slices before recording starts | -
+Activate Interaction | Click on Add in segmentation plugin
+Define output filename (be careful: plugin appends interactions to existing files) | SegmentationInteractor_AddTool.xml
+Start recording | Click on record symbol (red circle) in Event Recorder Plugin
+Perform Interaction | Draw a segmentation in the render window
+Stop recording | Click on stop symbol (red square) in Event Recorder Plugin
+Save record (\<interaction\>.xml) to your testing environment | MITK-Data/InteractionTestData/Interactions/SegmentationInteractor_AddTool.xml
+Save interaction result (Image, Surface, etc.) to your testing environment | InteractionTestData/ReferenceData/SegmentationInteractor_AddTool.nrrd
+
+\section Limitations Limitations
+<ul>
+ <li> No VTK interactions are recorded
+ <li> Renderwindows have to stay constant during record (e.g. no resizing)
+ <li> Interactions have to follow the new Interaction concept
+</ul>
+
+\section UsingInteractionsInTests Using Interactions in Tests
+
+In order to use interaction tests, the class mitk::InteractionTestHelper has to be used.
+The usage of this class is explained with an example of the SegmentationTool test.
+The TestHelper needs to know the location of the recorded interaction file.
+This is done by giving the filename to the constructor.
+
+\code
+//Create test helper to initialize all necessary objects for interaction
+mitk::InteractionTestHelper interactionTestHelper(GetTestDataFilePath(interactionPattern));
+\endcode
+
+The InteractionTestHelper stores its own DataStorage.
+We want to use this DataStorage and provide all necessary DataNodes.
+\code
+//Use data storage of test helper
+mitk::DataStorage::Pointer dataStorage = interactionTestHelper.GetDataStorage();
+
+//add images to datastorage
+interactionTestHelper.AddNodeToStorage(patientImageNode);
+interactionTestHelper.AddNodeToStorage(workingImageNode);
+\endcode
+
+Let the InteractionTestHelper know about the relevant time step (particularly necessary with 4D images)
+\code
+//set time step
+interactionTestHelper.SetTimeStep(timestep);
+\endcode
+
+When everything is set up, the loaded Interaction can be played back.
+\code
+//Start Interaction
+interactionTestHelper.PlaybackInteraction();
+\endcode
+
+
+
+
+*/
diff --git a/Documentation/Doxygen/DeveloperManual/Starting/AboutTesting/AboutTestingPage.dox b/Documentation/Doxygen/DeveloperManual/Starting/AboutTesting/AboutTestingPage.dox
index 79869a4d33..71f56ac001 100644
--- a/Documentation/Doxygen/DeveloperManual/Starting/AboutTesting/AboutTestingPage.dox
+++ b/Documentation/Doxygen/DeveloperManual/Starting/AboutTesting/AboutTestingPage.dox
@@ -1,13 +1,14 @@
 /**
 \page AboutTestingPage Testing
 
 Testing is a very important part of ensuring code quality. We use <a href="http://www.cdash.org/">CDash</a> for testing whether MITK builds on a variety of platforms and configurations. You can find our dashboard <a href="http://cdash.mitk.org/index.php?project=MITK&display=project">here</a>.
 
 Additionally we support tests of software function as well. More detailed information on testing in MITK can be found below.
 
 <ul>
  <li> \subpage GeneralTests
  <li> \subpage RenderingTests
  <li> \subpage DICOMTesting
+ <li> \subpage InteractionTestingHowTo
 </ul>
 */