I updated the document and added content to explicitly test

• segmentation on a 3D image
• 3D segmentation (static) on a 4D image
• 4D segmentation (dynamic) on a 4D image

I tried to shorten the instructions to not make the document too long. I think the new content makes {T26987} even more important. With a new format we could add subsections for different data types.
I copied the modified document to E130-Daten\Release\Checklisten\MITK Workbench Release and renamed it to Checkliste Segmentierung – 2D Segmentierung

just started to have a look.

My first -to be discussed- questions would be:
If we rework the checklists anyways, could we also switch languages or would that be a milestone for next time?

We discussed the open todos concerning Checklists (storage, format, language) and decided that this topic should be prioritized higher but not for the milestone of the new release / current documentation refactoring.
I think this would be a good option for the phase after the release but if you have a strong point to do it now, please state here.

I agree :)

I think the things you changed are all reasonable, the things I would add (I can not do it atm because I don't have access to the document)

The tester should check for static and dynamic

1. whether the segmentation result has the right dimensions
2. in case of dynamic segmentation, he/she should check whether the algorithm is applied on only the selected or on all timesteps

I looked again at the tests we have inside the checklist and I think it is still very long and many steps are redundant - because only the clicked tool-button changes and the underlying segmentation algorithm produces different results.
I think it is clearer and even better for testing a specific tool / algorithm, if we somehow separate the tests for different tools.
Also,

In T27507#211660, @thomass wrote:

If necessary, I might need a helping hand because static/dynamic*single/double*2DTools/3DTools = many test cases

So to reduce the size and complexity of the checklist I think we should try to

1. remove tests that can be automated
2. group / separate tests according to a reasonable similarity / dissimilarity
3. split the document into the clustered algorithms / continue with {T26987} for a better checklist format

Edit: We had a discussion about refactoring the segmentation tools. This will be explained in T27507#211912.

Segmentation tests with different labels / on different layers have been added because of T28142: [Segmentation] Remove plugin redundancy with MultiLabelSegmentation / D601.