When working on changes to the firmware core it would be desirable to have a generalized testing procedure that defines what must have been tested before submitting a PR. This is mainly important in those rare cases where a PR comes with changes to core header files.
It is certainly not possible to test all available features manually and only few of us might have all keyboards available that are supported by Kaleidoscope.
But in my opinion it would already be a good start to maintained a firmware sketch that includes all parts of the firmware, i.e. all core plugins and features, to make at least sure that everything compiles. This sketch would definitely not create a reasonable firmware for most devices as its binary would be way too large. But for a compile test that’s of no importance.
It would also be desirable to build this testing firmware for all supported hardware before submitting PRs that comprise changes to header files.
Devs, what do you think?