Archive for the ‘Uncategorized’ Category
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.
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.
This week is a release week. On Thursday, the Release Team will be releasing Maverick Alpha 2, the second development release for this cycle. As every release week, this is going to be a busy one.
- I am syncing my ISO images to have them more or less prepared when the first candidate images start to appear. I am using dl-ubuntu-test-iso to sync my ISOs. If you want to use it as well, you just need to install the ubuntu-qa-tools package.
- I am going to prepare some VM machines with different flavours of Lucid on it, to test the upgrades to Maverick as soon as possible.
- I will spend most of the week testing the different images and reporting back my findings to the ISO tracker. If you want to help with ISO testing this week, make sure you read the documentation first.
- On Friday, once Maverick Alpha 2 is released, I will be upgrading my own machine to Maverick.
For those unfamiliar with the title of this blog post, let me introduce you to one of the most important tags in Launchpad: regression-potential.
What bugs tagged as regression-potential mean? Basically, they mean that a regression has been found in the development release of Ubuntu (Lucid Lynx, at the moment of writing).
Why are they so important? Because it means that a regression has been found but, good news, we still can do something about it.
These bugs are specially important in the kernel. Nobody likes to see hardware, working in previous versions of Ubuntu, failing once upgraded to the new one.
Jeremy Foshee, a QA member of the Kernel team, is trying to avoid as many regressions in the kernel as possible. As announced in several mailing lists, he is going to be organizing a weekly bug day of kernel bugs marked as regression-potential from today and until the release of Ubuntu 10.04 (Lucid Lynx). If you want to help avoiding regressions in Lucid, every Tuesday, you can check the Kernel Bug Day page, which includes a list of bugs that need some love. If you have doubts on how to help, please, join the kernel team on #ubuntu-kernel at freenode IRC, and feel free to ask any question.
The more people helping triaging regression-potential bugs, the fewer regression-release bugs Lucid will have.