I see you've previously implemented travis-ci support, but now that travis are charging for all services, most Moodle developers with plugins in github are moving to using the free github actions to perform the same task -
template message below that covers github actions:
Some of the tests run by the Moodle.org plugins db can be run via github actions on each commit in your github repo. Enabling this helps you to make sure future changes to your plugin will continue to follow the guidelines.
then on every commit you make to github it will fire off a request to run the tests and will give you traffic lights beside each commit and generate a report.
I see you've previously implemented travis-ci support, but now that travis are charging for all services, most Moodle developers with plugins in github are moving to using the free github actions to perform the same task -
template message below that covers github actions:
Some of the tests run by the Moodle.org plugins db can be run via github actions on each commit in your github repo. Enabling this helps you to make sure future changes to your plugin will continue to follow the guidelines.
the short version - grab this file: https://github.com/moodlehq/moodle-plugin-ci/blob/master/gha.dist.yml rename it as ci.yml and put into the directory .github/workflows within tyour project eg: https://github.com/danmarsden/moodle-mod_attendance/blob/main/.github/workflows/ci.yml
then on every commit you make to github it will fire off a request to run the tests and will give you traffic lights beside each commit and generate a report.