You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixes#203 and #146
This solves two cases where moodle-plugin-ci was being "too
aggressive" managing the phpunit.xml files.
1. If the plugin comes with its own phpunit.xml file, give
to it absolute precedence, so it's not overwritten or modified ever.
2. If the plugin doesn't have any tests/coverage.php file,
instead of applying moodle-plugin-ci defaults, let's allow
core to apply its own ones. See MDL-72701 for more info
about core coverage defaults. We'll continue applying
our defaults for Moodle < 3.9.
Copy file name to clipboardExpand all lines: docs/CHANGELOG.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,9 @@ This project adheres to [Semantic Versioning](http://semver.org/).
9
9
The format of this change log follows the advice given at [Keep a CHANGELOG](http://keepachangelog.com).
10
10
11
11
## [Unreleased]
12
+
### Changed
13
+
- Plugin bundled `phpunit.xml` files are not overwritten or modified ever.
14
+
- For Moodle 3.9 and up, when the plugin is missing any `tests/coverage.php` file, core defaults (`lib.php`, `locallib.php`, `classes/`, ...) will be applied. Previously, all the `*.php` files were applied by default (note that older Moodle versions will continue getting them).
0 commit comments