If you have been helping testing MT and you’re name does not appear there, is due to a bug in the ISO tracker, that prevents testers that haven’t set their Launchpad ID properly. This bug has been fixed, and it will be released in our next roll out of the testing tracker, but, in the mean while, there is a workaround that I explained in a previous post.
Please, if you are helping testing uTouch, check out how to appear in the Hall Of Fame.
This year, due to family commitments, I was unable to attend GUADEC. Although the reason why I couldn’t attend made me very happy, I also was sad by the fact that I wasn’t going to be able to attend one my favourites FOSS conferences.
I have started downloading some of them and, of course, the first talk that I watched was the one given by my good friend, excellent hacker and accessibility advocate, Eitan Isaacson. In his talk, Eitan explains in a non technical way, why it is important to have accessibility in mind when designing any kind of products: from buildings to software. If you are a software designer or developer, I really recommend watching his talk. I am sure you will start thinking about accessibility when designing your next application.
Maverick is coming with multitouch & gestures support!
OK, right, this is not news, a lot of people have been already been talking about it, inside the Ubuntu community, and also outside the community. I cannot express how excited I am about multitouch support and the possibilities it opens (phones?, tablets?, the-next-great-small-device?). But, first, we need to test it!
So, maybe, you have a multitouch device. OK, maybe you don’t. Maybe you just have a single touch device (a touchpad, a tablet). OK, maybe you don’t. Maybe you just have a mouse. In all those cases we need your help. Obviously, our main interest is in getting feedback from people with multitouch devices, but, we also need to see if regressions were introduced in the process.
So, how can you help?
Setting Up Instructions
- Install the utouch package.
- You have to have an account in our tracking system.
- Go to http://multitouch.qa.ubuntu.com.
- Click on “Log In” and “Create New Account”
- Once you’re done with the tracker, subscribe the Ubuntu Multitouch dev mailing list, where you will be able to contact the developers in case you face any problem.
- If you want, send an email to the mailing list introducing yourself.
- You’re all set!
We will be announcing new testing cycles in the mailing list. The tests will appear in the tracker and everybody is free to submit their results any time, while the testing cycle is opened.
Every testing cycle, you will see the tracker (http://multitouch.qa.ubuntu.com) reset. You need to click on a set of testcases to see the list:
The list of testcases appear, with a summary on how many results have been reported:
To read the instructions on how to perform the testing, and report your result, click on any of them. The testcase view will show a form to report your result and a link to the testcase wiki, to guide you through the process.
|Please note that the link “Additional instructions are available” is actually the link to the testcase description. This is a wrong wording of the link and we will fix it in the next roll out of the tracker.|
If the testcase passed, just mark it as passed.
Utouch packages come with Apport hooks, that will make it easy to file bugs with the relevant information for the developers. To file a new bug please, open a terminal window and type:
$ ubuntu-bug utouch
After the relevant information has been collected, it will be sent to Launchpad, where you will be able to describe your problem. As easy as that! You have to love Apport!
You can also point to bugs that have been already reported.
Update: note that the images are cropped screenshots; to see the full text, please visit the http://multitouch.qa.ubuntu.com
A couple of weeks ago we launched the Desktop Testing Program. You can read more about it in the original announcement but, basically, we have some infrastructure to track test results for desktop applications, a wiki that stores the testcases description and a large community willing to test every Ubuntu milestone.
The Alpha 3 testing cycle went very well, but we still need more testcases to make the Beta testing cycle event better.
Mathieu Trudel-Lapierre, one of the Network Manager upstream developers, stepped ahead and wrote some testcases for Network Manager. He, as an upstream, wanted Network Manager to be part of the testing program, to have the opportunity to get test results every Ubuntu milestone. His tests will be part of the Desktop Testing Program starting on Maverick Beta.
If you are an upstream (or would like to collaborate somehow with your favourite upstream project), you can review the available tests in our testcases wiki, and, if the application is already there, make sure that the tests still apply and write more to cover new features. If your application is not there, just create a new page and start adding new testcases. In both cases you can follow our syntax guidelines.
I think this is a great opportunity for upstreams to have their project tested on a regular basis by a great community, with results they can browse, in a repeatable way. I just hope more upstreams could know about it. If only this blog was syndicated in Planet Gnome…
Today, one day after reaching the third Maverick milestone, Alpha 3, I am happy to announce the birth of a new testing project and team in Ubuntu: the Desktop Testing Team.
Every time we release a new Ubuntu milestone, testers are encouraged to install the new milestone and play around with it, filing bugs as they go. We want to go a bit further and use a more methodological approach for those people that love testing and want to help improving Ubuntu that way.
How will it work?
For every milestone of the development release of Ubuntu, we will be providing a series of testcases for you to run in that milestone. As soon as the milestone is officially released, you will be able to complete the tests in the following two weeks (although we encourage you to run them as soon as possible, to allow enough time for developers to fix the bugs).
One of the good things about this program is that you, as testers, will be able to know every time what to test, you will be able to check the new features before anybody else, and you will gain experience on the Ubuntu development process. Also, there will be a mailing list to share your experiences, bugs and to have direct feedback from the developers.
We will we using a test tracker to track your results and positive feedback (a test passed correctly) will be also really helpful. Right now, if things are working correctly, the developers need to guess it from the lack of test reports.
When will it start?
Just now! Although we don’t have a lot of testcases yet, we wanted to start the program just after the release of Maverick Alpha 3. The first weeks of the program are going to be busy and fun. Apart from testing and updating results, we are going to be introducing ourselves in the mailing list, commenting what testcases need updates and what applications we need to add when we reach Maverick Beta.
How can I participate?
Start by joining the Launchpad team and subscribe to the mailing list. Introduce yourself in the mailing list, tell us about you and what applications are you mostly interested in. Create an account in the tracker (if you already have an account at iso.qa.ubuntu.com it will work as well). Blog about it, tell your friends, tweet it. And, of course, start testing Maverick Alpha 3. We are going to make Ubuntu better. And GNOME. And many other applications that are part of Ubuntu.
You can find the full documentation on how to test on the Desktop Testing wiki page.
As Martin Pitt announced, we are in the Maverick Meerkat Alpha 3 release week. As for every milestone, we will be coordinating the testing of the different images we produce in the ISO Tracker. This time, however, the ISO Tracker comes with some new features (and some bug fixes) that will make your testing easier.
Coverage report is back (including optional testcases!)
After way too many milestones and releases, the coverage report is back again! This report is useful to see what testcases need some testing, and which ones haven’t been covered. This is special important for optional testcases, that are now included in the report. Optional testcases are testcases that do not need to be covered for every image but that need to be covered at least once. Visiting this report testers will clearly see which optional testcases have not been covered. So, go ahead, use this new feature, and cover some of those not-so-optional testcases!
Started tests in the landing page
In the global list of images, apart from the finished tests and the tests that failed (in red), we do have now the number of testcases that have been marked as “Started”. This number is shown in yellow.
“Not Complete” Filter
Apart from the usual status filters, we have included the “Not Complete” filter, which will show the images that have at least one uncovered testcase.
Delete your own result
Testers were complaining that, if the marked a test as Started and then something prevented them from finishing the test, they couldn’t delete their results. Now it is possible to delete your own results. If you made a mistake, nothing prevents you from going back.
Improved administrator interface
Although this feature will only be useful for administrators, I wanted to include it in this list. Apart from adding new milestones and builds, now it is also possible to add new products and new testcases using the web interface. This will accelerate the addition of new products and will help other teams to adopt the ISO Tracker quicker.
Actually, and as a beta of the new feature, you can now check the ISO Alpha 2 heroes at the Ubuntu Hall Of Fame under “Top ISO Testers”. If you are wondering why you are not there and you helped during Maverick Alpha 2 ISO testing, I will try to explain why.
The ISO tracker and Launchpad are not connected, but we need to use the Launchpad ID in the Hall Of Fame to get some other user information. Fortunately there is a Launchpad ID field in your ISO tracker user profile.
So, if you want your awesomeness to be reflected in the Hall Of Fame, please, update your profile in the ISO tracker and fill your correct Launchpad ID.