Everybody is blogging about it, so do I.
Tomorrow I will be travelling to Gran Canaria to attend the Desktop Summit.
If you're interested in testing, I will be presenting Mago on Wednesday.
I hope to see you there and meet a lot of new people!
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.
As announced in the LDTP mailing list, LDTP 1.5 is out.
This new release contains some nifty new features:
- Log all failures and take screenshot on each failure
- Create default log file in /tmp/ldtp-$USER
- Screenshot using pygtk, instead of ImageMagick import, when possible
- Added new api – appundertest
We are specially happy for the screenshot feature, for which we had specially pushed for, to have better reporting options. You can see an example of a report at the QA site.
Also, if you’re running Jaunty, you can start using LDTP 1.5 new features with ubuntu-desktop-testing, using the reporting_ldtp_1.5 branch (soon to be merge into trunk), as LDTP 1.5. is already in the archive 
Thanks Nagappan and the rest of the LDTP dev team for the best LDTP release to date!
Next Thursday Januanry 15th the Bugsquad team is organizing their first Ubuntu Bug Day of the year.
The chosen package this time is network-manager. Please, read the details at the event wiki page.
Go ahead! Triaging bugs is a great way to contribute in making Ubuntu better!
At the QA team we are going to organize Testing Days to cover new features for Jaunty.
It has happened before that a new feature well documented with its blueprint and its spec never gets tested and it happens to have a major bug that it is only found very late in the cycle.
We are trying to minimize these cases organizing special Testing Days to cover such features. So, if you’re developing a new feature and want it to be tested in a Testing Day, please, add the feature to the list in the wiki, so we can schedule it.
We will soon announce the next Testing Day and instructions on how to participate in helping to make Ubuntu better.
LDTP team just announced the release of a new version of LDTP, the testing framework that we are using at Ubuntu for our desktop tests.
The official announcement:
We are proud to announce the release of LDTP 1.4.0. This release features number of important breakthroughs in LDTP as well as in the field of Test Automation. This release note covers a brief introduction on LDTP followed by the list of new features and major bug fixes which makes this new version of LDTP the best of the breed. Useful references have been included at the end of this article for those who wish to hack / use LDTP.
About LDTP:
Linux Desktop Testing Project is aimed at producing high quality test automation framework (C / Python) and cutting-edge tools that can be used to test Linux Desktop and improve it. It uses the Accessibility libraries to poke through the application’s user interface. The framework also has tools to record test-cases based on user events in the interface of the application which is under testing. We strive to help in building a quality desktop.
Whats new in this release:
Added new APIs for VMware Workstation automation
Initial work for LDTPv2 – LDTP engine in python
Added code block specific to Access Company related environment
Improved LDTP performance, by reducing the number of window information lookup
Access company has contributed significant code to perform on multiple window without titleBug fixes:
* Guofu Xu fixed couple of crash, handled new scenarios where the window title is empty and many other performance improvement.
Fixed bug # 343890, 550978
Fixed thread lock, which avoid the crashDownload source tarball -
http://download.freedesktop.org/ldtp/1.x/1.4.x/ldtp-1.4.0.tar.gzLDTP news:
More news to come later
References:
For detailed information on LDTP framework and latest updates visit http://ldtp.freedesktop.org
For information on various APIs in LDTP including those added for this release can be got from http://ldtp.freedesktop.org/user-doc/index.html
Congratulations team on a great job!!
Ubuntu 8.10 (Intrepid Ibex) was released a couple of weeks ago. You had the time to play around, see the cool new features and start missing those that are not there.
The Ubuntu Brainstorm is the place to add that kind of cool things that you would like to see in the next release of Ubuntu. So, if you have a “hey, it would be great if…” for the next release you’d better be adding it to the Ubuntu Brainstorm, so people can vote for it before the next UDS.
Come on! Dream!
We are pleased to announce the next Ubuntu Testing Day, that will be next Monday, November 10th.
The Ubuntu Testing day is a special day where the Ubuntu Community comes together with a shared goal of testing a specific set of ISO images (Alpha, Beta, RC, Gold or Point releases), a specific feature or some bugs needing verification. Taking the idea from the Ubuntu Bug Day, we want to apply the same concepts to ISO testing.
Who can join the Testing Day?
Everyone. You don’t need to be a developer. You don’t need to know how to code. Everyone is welcome. If you don’t know how to help, then just stop on by and we’ll explain everything to you. In fact, one of the objectives of the Testing Day is to help people willing to start testing Ubuntu to make it better.
Where to join the Testing Day?
Come to #ubuntu-testing on freenode IRC. We will be there day and night resolving your testing questions you might have. Normal testing activity takes place in #ubuntu-testing at other times also.
Which is the goal for this testing day?
We know we just released Intrepid a week ago, but we have a lot of pending SRU bugs in Hardy needing verification. Hardy is a LTS release, and therefore it needs to be kept in shape for a longer period. SRU is the process to get updates into a stable release. Please, refer to the SRU wiki page for more information on the process.
Please, join us next Monday and help to make Ubuntu even better!
A couple of weeks ago I had the opportunity to attend GTAC (Google Test Automation Conference) in Seattle (WA).
Although there were not many open source people there were a lot of open source lovers. Many of the speakers described how they use OSS to test their applications. In any case, it was really helpful attending a conference with so many professionals interested in testing automation. Some of the talks are already available in youTube. Expect more to come in the next few days.
Hopefully next year we will have a talk about testing automation for Ubuntu
We are pleased to announce the next Ubuntu Testing Day, that will be next Monday, October 6th.
The Ubuntu Testing day is a special day where the Ubuntu Community comes together with a shared goal of testing an specific set of ISO images (Alpha, Beta, RC, Gold or Point releases). Taking the idea from the Ubuntu Bug Day, we want to apply the same concepts to ISO testing.
Who can join the Testing Day?
Everyone. You don’t need to be a developer. You don’t need to know how to code. Everyone is welcome. If you don’t know how to help, then just stop on by and we’ll explain everything to you. In fact, one of the objectives of the Testing Day is to help people willing to start testing Ubuntu to make it better.
Where to join the Testing Day?
Come to #ubuntu-testing on freenode IRC. We will be there day and night resolving your testing questions you might have. Normal testing activity takes place in #ubuntu-testing at other times also.
Which release we will be testing?
Apart from testing the beta ISOs, we will be focusing on testing distribution upgrades.
If you want to upgrade your Hardy system (*buntu 8.04) to Intrepid (*buntu 8.10) this is a great way to help on your way.
Also, the great and fun Marc Tardiff (cr3) will be giving a session at the #ubuntu-classroom IRC channel (15h UTC) about the testing infrastructure, giving an overview on the tools available to make Ubuntu testing easier and funnier.
Please, join us next Monday and help to make Ubuntu even better!
