Ubuntu Wiki

DRAFT

Summary

The purpose of this document is to explain the different testing efforts for Unity in the Natty cycle.

Automated Testing

Unity itself

Although the DX team is the main responsible of testing the Unity interface itself, we need to collaborate with them so our tests work better.

Unity itself is not accessible, so the Unity interface cannot be accessed directly with the tools we have right now. Luckily, Mago is tool agnostic and, although is mostly based on LDTP, we can add other tools to help us testing the interface itself.

The Unity team will provide with a dbus interface that will allow us knowing the state of the interface at any given time. That will help us checking if the icons are showing correctly.

Xpresser, which is based in image comparison, is not suitable to check the state of Unity after running a test, as the design will change a lot during the Natty cycle.

Applications on Unity

The applications on Unity can be tested using the same a11y tools that we already use for the 2D experience. One of the main caveats is that Unity does not run under Xvfb and, therefore, we cannot run it on a server without having a full desktop up and running.

ACTIONS

• Research on how to run the tests using Hudson (or something else) in an automated fashion
• Run the mago tests on Unity at least twice per week in a machine with Unity running as mean time solution
• The tests results will be publicly available

Xpresser, although based in image comparison, can be good to launch applications from the launcher, as it is not accessible yet, and the icons don't tend to change that much. We need to be careful, though, as Xpresser is not being actively maintained and there could be some bugs.

2D Experience

The 2D experience needs to be tested as well and, actually, as the 2D experience runs well in a Xvfb, it will be easier to run using Hudson, without

ACTIONS

• Run a Hudson server on the datacenter
• Run a cronjob to update the system on a daily basis
• Run the mago tests on a daily basis in an automated fashion

Manual Testing

ISO Testing

As part as our per milestone testing, we need to be testing Unity on desktops and the 2D experience fallback. Many of us use VMs to test the images and we need to find a VM technology capable of running Unity.

Also, we need to modify the testcases (or add new ones) to match the new possibilities.

ACTIONS

• Communication with the installer and design teams to modify the testcases
• Include the new testcases into the ISO tracker

Desktop Testing Program

The Desktop Testing Program started last cycle and it provided a good way for the community to test the desktop applications every milestone. As part of the modifications for this program in the Natty cycle, we will be including Unity as part of the program.

For each of the applications, we will be duplicating the testcases, to be run in Unity and also the 2D experience.