The idea would be that a user can specify 2 default profiles in the .busted file. One to use interactively, and the other one being the CI default.
If there is a .busted file, then the default profile is called default. If a profile is specified that doesn't exist, it will automatically fall back to the default one again.
So with the new Busted GHA, we could add a parameter for the action; the profile to use for testing. And then set that default to ci for example. Because if no ci profile is specified, it will still use default.
Trick would be that f the user specifies it's own profile eg. --run=unit, then that should be honoured in favor of the ci one. This can be done by specifying the ci one first on the commandline, since the last option wins.
Based on discussion here: https://github.com/lunarmodules/busted/pull/698#issuecomment-1230137675
The idea would be that a user can specify 2 default profiles in the
.bustedfile. One to use interactively, and the other one being the CI default.If there is a
.bustedfile, then the default profile is calleddefault. If a profile is specified that doesn't exist, it will automatically fall back to thedefaultone again.So with the new Busted GHA, we could add a parameter for the action; the profile to use for testing. And then set that default to
cifor example. Because if nociprofile is specified, it will still usedefault.Trick would be that f the user specifies it's own profile eg.
--run=unit, then that should be honoured in favor of thecione. This can be done by specifying thecione first on the commandline, since the last option wins.So in the GHA we execute busted as;