Page MenuHomePhabricator

[Checklist] GUI test data originates from different sources
Closed, ResolvedPublic


Data in checklists originate from

  • Networkdrive -> Old 3M3 folder
  • MITKData
  • ...

and often no information is given (example: ImageRendering --> Thomas K mini3D ?)

Should we define one (open) accessible folder with:

  • Demo data
  • GUI test data
  • Unittest data

Should we use MITKData as storage?

Should we (re-)think "suitable" test data? Otherwise 90% of the checklists might be tested with Pic3D.nrrd

Event Timeline

thomass triaged this task as Normal priority.Jan 10 2020, 8:45 PM
thomass created this task.
kalali renamed this task from [Checklist] GUI test data originates from different sources to [Checklist] GUI test data originates from different sources.Sep 11 2020, 11:47 AM
kalali raised the priority of this task from Normal to High.EditedApr 22 2021, 12:11 PM
kalali added a subscriber: kalali.

I set the priority to high because we defined that having appropriate data at a reachable location is one of the most pressing issues when it comes to manual GUI tests.

We also decided to include more and foremost 4D test data and openly accessible test data.
We can also think about synthetic test data.

kalali claimed this task.
kalali moved this task from Cycle to Tests/Checklists on the MITK (v2021.10) board.

Obviously it was not clear what we are expecting here so I will close this task and refer to two new tasks for the specific topics mentioned here: