It would be great to only need to add additional extensions to CI instead of disabling things (e.g. when certain things aren't required based on included files)
The only concern if scanning one particular path is missing any for subplugins, but they might still use behat tests for the main test path (typically tests/behat/my.feature, but would be good to confirm this.
It would be great to only need to add additional extensions to CI instead of disabling things (e.g. when certain things aren't required based on included files)
With behat tests, it can probably be safely disabled if there are no behat feature test files included (examples: https://grep.app/search?q=Feature%3A&case=true&filter[repo][0]=moodleou/moodle-qtype_pmatch)
The only concern if scanning one particular path is missing any for subplugins, but they might still use behat tests for the main test path (typically
tests/behat/my.feature, but would be good to confirm this.