Testing without launching graphical components

jhlegarreta
Tue, 31 Oct 2023 14:19:16 +0000
Development

Hi,
I am trying to set up a GHA workflow to test the SlicerDMRI extension. ctest is effectively finding and triggering the tests so far:
ENH: Test build · SlicerDMRI/SlicerDMRI@576ae7c · GitHub

However, as I’ve realized locally, some of those tests launch Slicer’s GUI components, and thus fail in the GitHub headless testing environment. I’ve seen that the test command contains a number of flags, e.g.
ENH: Test build · SlicerDMRI/SlicerDMRI@576ae7c · GitHub

Including e.g. a --no-splash.

I am wondering whether tests we can completely avoid launching Slicer’s GUI parts, or whether this is the case already, and if tests fail, it is because they genuinely launch GUI parts (within the context of the extension, maybe due to some design choices). I am asking this to save installing xfvb (and spending time interacting with GHA to see if the steps work) if possible.

Even when a display is available, I’d say that it is not desirable to launch GUI parts.

Thanks.

3 posts - 2 participants