This is a gently reminder that it is still not late to test and update your plugins against upcoming Moodle 3.3. As a reward, plugins having a 3.3 compatible version available on the release day, will receive the special "Early bird 3.3" award in the Plugins directory.
This special medal was first awarded in 3.0. It is nice to see the increasing numbers of plugins that have been getting it since then.
The release of Moodle 3.3 was postponed for a week and is scheduled to happen on Monday 15 May 2017. Still enough time to
- Test your plugins intensively against Moodle 3.3 beta (Behat and PHPUnit tests help a lot).
- Fix all eventually raised warnings, notices, regressions and problems.
- Release a new compatible version in the plugins directory, or mark the existing one as compatible.
As always, we reserve the right to not grant (or even revoke) the award from a plugin if there is a suspicion that it was not tested well. There will be no exceptions for late submissions.
Big thanks to all the plugins maintainers for keeping their plugins up-to-date with new Moodle versions.
None of my Behat tests pass in 3.3, whereas they all pass in 3.2. Is there a document that describes what changed and what we may have to do to upgrade our Behat tests for 3.3?
I found that for most of my plugins it was the change to the Course Overview block that broke them, because I assumed that I'd have an active link to a course after logging in as a student or teacher. Starting them on the course homepage with the 'I am on "Foo Course" course homepage' step resolved the issue. See https://github.com/LafColITS/moodle-report_roster/commit/e6a9b046afd42ef65c5ed878aa06e60be202e20f for an example.
Charles
Thanks. I don't think that is the current problem, but will be once I get them running. I'll get set to make those changes.
mike
I have started a documentation page that I hope that we can continue to use from now on to clearly communicate behat compatibility changes between releases:
https://docs.moodle.org/dev/Acceptance_testing/Compatibility_changes
Any feedback or improvements to that page are very welcome. I'm sure there are some things I've missed, so feel free to fill the gaps. Thanks!
(I hope that over time compatibility breakages will be reduced as we have more step definitions which are robust to changes)
It is hard to answer without knowing what particular Behat failures you have. In either case, there is a bunch of Behat related changes documented at the main upgrade.txt and other changes are described in individual upgrade.txt files for each plugin type (as usually).
If anything is missing, please feel encouraged to search the tracker for issues that affected the Behat failures. Chances are the documentation is still on a todo list.
Thanks David -
If the upgrade document describes changes we may need to do to our Behat tests for 3.3, then that's what I was looking for. I'll go through that.
edit...
I don't believe I'm even getting to the actual Behat tests. Each scenario is posting this error:
" BeforeScenario # behat_hooks::before_scenario_hook()
unknown error: cannot get automation extension
from unknown error: page could not be found: chrome-extension://aapnijgdinlhnhlmodcfapnahmbfebeb/_generated_background_page.html"
mike
I'll repost that error in the testing forum.
Thanks to all maintainers for updating their plugins in time for the Moodle 3.3 release. Total of 153 plugins in the plugins directory have declared compatibility with Moodle 3.3 on Monday 15th May, 23:59:59 UTC. Once again, I am particularly happy to see even more plugins this time! You are a great community to be part of
I'm disappointed with myself that once again I did not get there in time
Well done evenyone who did.
Yes, good news
And the link to plugins having Early bird 3.3
As i'm curious, would it also be possible to mention somewhere the total number of plugins on the release dates, or the percentage of total plugins being "Early bird" at the release dates?
The total number of published plugins is displayed at the front page of the plugins directory. I'll try to remember to include the figures as percents next time, thanks for the suggestion (you are the third person suggesting that to me today )