Hi all, I just noticed that the whole section of Moodle Control (QA) on docs.moodle.org is missing (see: http://docs.moodle.org/en/Development:Overview#Quality_control). Just curious, does anyone know how moodle core team (or HQ) handle QA issues? Who are the main QA testers right now and what is the current work flow? Thanks!
Martin only started writing that development everview page a few days ago (according to recent changes) and it is not finished yet, so you probably just need to wait and see.
Moodle.com does not employ any testers as such. Like most things in an Open Source project, testing is distributed throuhout the world. Lots of Moodle users are also tester (more so than are developers).
Obviously, the tracker is the main interaction point between testers and developers.
There is also a Moodle QA team of volunteers that started about a year ago. They keep an eye on the tracker, and when a developer marks a bug resolved, they go and test tomake sure the fix works and mark it closed. That is the idea anyhow.
In generaly, on of the reasons that Open Source software tends to be quite bug free is that it is run in lots of different ways in lots of different places, and users are incouraged to report bugs they find. So the software gets a lot of testing, even if it is all rather ad-hoc.
Finally, some of the larger institutions that deploy Moodle do have professional software QA teams. For example, every time we deploy and update to the OU's Moodle install, we unleash our Technical Testing team of about six testers on it for about four weeks, and they test a wide range of functionality on all the browsers we support - and there are people in that team who have an amazing talant for breaking software. Still, better that they do it than our students. Also, as we develop new pieces of functionality between releases, they also do some initial testing when each feature is finished. Finally, we occasionally invite students in for usability and accessibility testing.
Moodle.com does not employ any testers as such. Like most things in an Open Source project, testing is distributed throuhout the world. Lots of Moodle users are also tester (more so than are developers).
Obviously, the tracker is the main interaction point between testers and developers.
There is also a Moodle QA team of volunteers that started about a year ago. They keep an eye on the tracker, and when a developer marks a bug resolved, they go and test tomake sure the fix works and mark it closed. That is the idea anyhow.
In generaly, on of the reasons that Open Source software tends to be quite bug free is that it is run in lots of different ways in lots of different places, and users are incouraged to report bugs they find. So the software gets a lot of testing, even if it is all rather ad-hoc.
Finally, some of the larger institutions that deploy Moodle do have professional software QA teams. For example, every time we deploy and update to the OU's Moodle install, we unleash our Technical Testing team of about six testers on it for about four weeks, and they test a wide range of functionality on all the browsers we support - and there are people in that team who have an amazing talant for breaking software. Still, better that they do it than our students. Also, as we develop new pieces of functionality between releases, they also do some initial testing when each feature is finished. Finally, we occasionally invite students in for usability and accessibility testing.
Hi,
like Tim said, this page is new, so still not finished.
Helen as put some information about QA today
like Tim said, this page is new, so still not finished.
Helen as put some information about QA today