In the meeting today we (@pieper, @lassoan, @mau_igna_06, @Sam_Horvath, @Connor-Bowley, @RafaelPalomar) were discussing about some of the extensions tests failing due to missing dependencies during testing (https://github.com/Slicer/Slicer/issues/6529)
One interesting idea that came up in the discussion was to do individual extension testing in separate containers where the dependencies are pulled-in (and possibly installed in the testing container); apparently dependencies in some extensions might alter the Slicer environment making other extensions not compatible. Along with this idea, there was a discussion on whether we could create/support infrastructure to allow developers to do the testing on their own with github actions or similar. This would effectively make the testing distributed, reduding the testing burden for the Slicer project.
@jcfr, as we have discussed the extensions testing before, it would be nice to know your thoughts on these ideas.