Martin Dougiamas

Thanks Ludo, looking forward to that.

Thanks Gordon, you are doing some amazing work.

Unfortunately these new core APIs are still changing even now as we work with them (eg MDL-21235)... Upgrading code to work fully with Moodle 2.0 is going to cause significant work everywhere ... the results are worth it but it's a long hard road. That's why I'm being very conservative about adding new modules in 2.0 core right now.

Keep in touch about HotPot and let us know if we can help. We've already been doing a lot of maintenance on it in the past months.

Moodle 2.1, on the other hand, is going to have all the core team focussing exclusively on popular activity modules, blocks etc. (dance) I'm really looking forward to that.

Hi Mary,

At this point there are no plans at all to include TaskChain or Quizport in Moodle 2.0 core and I would not expect it to be in there at this late stage. It's possible it could make 2.1 or later if it is popular and passes coding reviews etc.

It can of course be installed separately into a 2.0 installation as a 3rd party contributed module.

The current plan is to keep Hotpot in 2.0 for the time being with minimal maintenance work only, so that people upgrading at least won't lose any functionality.

As Tim said, we did try Selenium ages ago and we found such tests pretty fragile in Moodle because of all the different settings we have. We'll end up spending a lot of precious developer time creating/maintaining a test framework.

This is one thing the non-developer community can easily help with, so why not let them help?

Human testers can spot things that are not directly in the actual test, they can also link to other issues in the tracker if necessary, come up with better interface ideas, communicate directly with developers about issues, and generally help us in all kinds of ways Selenium alone can not.

Of course I'd be very happy if someone is offering to build and maintain a comprehensive Selenium test suite, it would be useful, but I don't think it's a good use of core developer resources right now, that's all.

Nothing I know of, except perhaps the debugging mode itself Try turning all the Moodle debugging off and make sure you clear the browser cache - does it help?