Mago – A Desktop Testing Initiative

A year ago I started a project, as part of my work at Canonical QA team, that aimed to have a consistent way to add automated desktop tests to Ubuntu. That project was originally called Ubuntu Desktop Testing.

The project grew and as the GNOME testing community started to be interested in it, we created a mailing list and an IRC channel (#gnome-testing at irc.gnome.org) for the GNOME folks.

The problem about having two projects (one for Ubuntu and one for GNOME) is that it was very difficult to maintain both synchronized. Also, having the project named as another project (Ubuntu Desktop Testing, GNOME Desktop Testing…) confuses people, as they think that it is exclusive for Ubuntu and/or GNOME, which is not true (as soon as AT-SPI gets migrated to D-BUS KDE will also benefit from this effort, i.e.).

So, today, I am pleased to announce “Mago“, a desktop testing initiative that will replace the other two and that can be used to create desktop tests for any AT-SPI enabled linux desktop.

Mago is hosted in Launchpad at https://launchpad.net/mago and you can start adding test cases by just creating a branch of your own and propose merges as you go by.

The trunk branch is owned by a Launchpad team, mago-contributors, that it is a moderated team. Once you have contributed through merge proposals, you can apply to be part of the team and will be able to push to trunk and review some other members contributions. Join us!

Happy testing!
Ara.

P.S. For those interested, “mago” stands for “magician” in Spanish.

5 comments

  1. Do you need test cases to test mago’s ability to handle test cases?

    More seriously, does Mago require copyright assignment to Canonical like other Canonical initiated codebases? I don’t see Mago listed at
    http://www.canonical.com/contributors but I don’t want to assume that list is accurate either.

    A little clarity would be helpful. This is the sort of licensing detail the Launchpad summary page doesn’t expose.

    -jef

  2. Groovy, I would be really interested in helping out with the KDE efforts. I have been following the QA teams work in preparation for the moment the AT-SPI stuff is ready for KDE. If you have any advice or pointers that I should be looking at further than I have thus far, you can ping me on IRC (nixternal). Thanks Ara!