I started with the checklists I from E130-Daten\Release\Checklisten\MITK Workbench Release.

Edit: I see this as a meta-task so I didn't claim this one. Please go ahead and choose / create a subtask for other checklists.

All tools have to check for the following usage scenario:

• All this with an image which time geometry does not start at 0 ms (e.g. MITK-Data/3D+t-ITKIO-TestData/LinearModel_4D_arbitrary_time_geometry.nrrd)

For this I would like to refer to T26989: [Checklist] GUI test data originates from different sources to discuss a new set of test images.

Damn I have forgotten to copy the checklist to a reachable share. @kalali Is it already done now or obsolete?

What exactly? I copied the checklists to my local machine and I'm working on T27716: Extend "Checkliste Segmentierung – Manuelle Segmentierung / 2D Segmentierung".

The checklist don't say anything about multilabel segmentation. This should be addressed with a special focus on creating and combining multiple labels / layers.
I couldn't find any other checklist with a focus on the multilabel functionality.

OK. But I tend/think more and more that we should strive for a unit test testbed that tests all that on the tool class level (either the respective base classes or the tools itself where it is easily possible (e.g. because the have no interaction (but even thous shouldn't be a show stopper).

So before anyone does extensive checklist rewriting or checking, please evaluate the possibility to directly invest more into unit tests.

I'm all in for that. We already discussed that we will focus again on this task {T26754} and its subtasks. This also includes

Automatic GUI testing

and

move as much tests as possible to Unit-Tests

So I'll agree. After the existing segmentation checklists have now been re-checked, we could use them and start reducing the manual tests there, as mentioned

In T27716#211856, @kalali wrote:

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

@kalali That is a good idea and proposal for how to proceed.

All checklists have been refactored and used again for testing MITK 2022.04.
Some issues with the checklists still exist, so I will use this task to fix these for the upcoming release:

• Checklist tools screenshot needs to be updated
  • 
  • Fast marching 2D is missing
• MultiLabel color map could be improved
  • was previously known as T28493: Multilabel color map colors are not very nice
  • solved with 827c3bebc9dc!
• Description doesn't seem to be intuitive
  • 
• Warning message for interpolation
  • Also showing a text that interpolation is not available

Edit: Segmentation checklists have been updated.

Related: T29088: [Checklist] 3D Segmentation - Checklist and MITK UI Inconsistencies