You now have to use -Dpreview-server-tests to enable testing of WF Preview. So ideally that drives any consideration of "what WF variant are we testing" and then other props drive "what modules are we executing" and "how are we executing".

So, see if -Dts.preview can become more like std wf (e.g. -DallTests) and -Dts.bootable.preview can become a flavor of -Dts.bootable.

It's not clear this can work, at least with Maven 3 (perhaps Maven 4 is better). The problem is profile activation can't be based on multiple factors, e.g. -Dpreview-server-tests and -Dts.bootable. So if we want to configure bootable jar testing in a particular way in say, ts/int/basic, but only if we're testing WFP, that might not be possible.