udisks2 will be the default backend for gnome/unity in Quantal:
https://wiki.ubuntu.com/QuantalQuetzal/TechnicalOverview/Alpha1#Ubuntu
The current version works well for udisks version 1 but we should add the support for udisks2 as well:
http://udisks.freedesktop.org/docs/latest/ref-dbus.html
== Importance==
This feature is pretty important to have as currently all the storage tests are broken; they do not work on Quantal and will produce failing results even for users with working hardware. This code enables these features to work correctly under Quantal.
Udisks2 does not provide some bits of information that udisks1 does, and which are necessary to have coverage of all device types that checkbox can test (usb 2.0 and 3.0, memory cards, esata, firewire). So the code is somewhat extensive to account for all these use cases.
A few changes to job definitions were needed (the addition of --memorycard parameter) since it's needed for memory cards to be properly recognized.
== Risk assessment ==
The udisks2 code was developed in an incremental fashion. Due to the
requirement that the same code base keep working on Ubuntu 12.04, the changes
were done carefully to minimize breakage.
Since udisks2 introduces a few API changes and removes certain properties the
old code depended on, particularly speed reporting which is needed for proper
USB 3.0 testing, some refactoring was needed to abstract these changes and keep
the code as clean as possible. Unit tests for these components help ensure
there's no breakage while changing code. While developing, many tests with
actual hardware were performed to ensure that device detection and testing was
reliable and failure scenarios were handled properly.
Once all the parts were ready to land, the udisks2 code was integrated and
merged into checkbox. During this phase the code continued to be tested with
actual hardware to guarantee that all the pieces "fit together" correctly and
the end result worked adequately.
Once everything was in place, two sets of tests were performed: a set of tests
to ensure the features worked as required, and validate that nothing had broken
during final integration. Finally, when preparing the Ubuntu upload, a package
was built and the scripts were tested from the sort of installation an end-user
would see.
Since the code was very extensively tested during development, we believe the
risk of including this to be rather low, and any impact would be localized to
the storage device testing section of checkbox, so the symptoms would in any
case be very easy to identify and clear to solve. Despite this, during testing
all the code behaved properly so if any, the potential remaining problems
should be corner-cases unlikely to have a widespread impact.
== Testing ==
We tested building the package (build log is attached as a comment), installing and upgrading (logs also as comments). We also redid our manual testing by launching the modified scripts (removable_storage_watcher and removable_storage_test) with various parameters (especially the -m and -p parameters used to test for devices with specific speeds, to validate in particular that usb 3.0 devices are testable) and different kinds of devices. The scripts work well and as expected.
This has reared it's head in weekly testing:
Traceback (most recent call last): File "/usr/lib/