moodle-plugin-ci
moodle-plugin-ci copied to clipboard
moodlehq
Helps running Moodle plugins analysis checks and tests under various CI environments.
Right now we have the `codechecker` command that reports all the issues found by `phpcs`. This is useful locally and @ CIs. Also, there is the `codecbf` command that also...
Current implementation are 95% the same, and it wouldn't be crazy to make them share all the common bits. There are various approaches to this: - make one to extend...
All tests are performed with `bin/moodle-plugin-ci` and that's ok and cover 99% of uses. But it's also possible to download `moodle-plugin-ci.phar` and use it on any moodle directory. 99.99% of...
This will be useful to achieve a series of tests running behaviour similar to Travis, while running in different environment (e.g. GitHub Actions or GitLab). We got something similar already...
Consider creating a dedicated [Action](https://docs.github.com/en/free-pro-team@latest/actions/creating-actions) for `moodle-plugin-ci`, and list it in the marketplace (good example [PHP Action](https://github.com/marketplace/actions/setup-php-action)), so that developer who want to enable CI for their plugin would only...
Install command verbose output contains false `ERR` states (at lines that are not really errors): ``` 195.45s$ moodle-plugin-ci install -vvv [info] Starting install [info] Cloning Moodle RUN git clone --depth=1...
Currently the plugin works in a way that behat/phpunit initialisation happens as part of install step irrespective whether ci script contains those tests or not. The logic is based on...
As Symfony 3.4 support comes to end in 11/2020, we need to switch Symfony packages to current LTS version: https://symfony.com/releases/4.4
This currently fails on plugin-ci test itself and ~~on fixture plugin tests using master and 3.9.~~ (addressed in #16)
Recently we have started to run behat tests using dockerized browser + selenium. Right now, and until we get the webdriver drives updated to newer W3C ones in behat... we...