Several apps have failing tests with 20131003 ui-toolkit

[Timo Jyrinki]

As discussed on IRC, upgrading to ubuntu-ui-toolkit version from today breaks all weather app tests, 3/7 terminal app tests, 2/2 rssreader app tests (https://pastebin.canonical.com/98420/). No further app testing was done because of the found reproducible problems. Reverting to archive version of ubuntu-ui-toolkit immediately fixed all the failing tests.

ui-toolkit's own AP tests function alright.

[Pat McGowan (pat-mcgowan)]

before these changes, the path was something like:
 ~/.local/share/Qt Project/...
 after it is something like:
 ~/.local/share/$applicationName/...

If tests are coded to look at the previous path they will need updating.

[Pat McGowan (pat-mcgowan)]

The fix for bug /1231863 seems to have triggered this

[Francis Ginther (fginther)]

Looks like the problem is that the apps hardcoded the db path which has now changed via the fix for lp:1231863.

Example from weather-app:

 'dbs_path = os.path.expanduser("~/.local/share/Qt Project/QtQmlViewer/QML/OfflineStorage/Databases/")'

[Nicholas Skaggs (nskaggs)]

This bug I believe is related: https://bugs.launchpad.net/ubuntu/saucy/+source/qtdeclarative-opensource-src/+bug/1197051

[Pat McGowan (pat-mcgowan)]

Is it possible to provide a library call of some kind that properly constructs the path using the right app name? Then all tests use that rather than a hardcoded path.

[Nicholas Skaggs (nskaggs)]

The long term plan is to use a property via the UITK emulator for this. This is considered the short-term fix so we can land this stuff. Leo is working on the changes to the emulator to support this idea.

[Jamie Strandboge (jdstrand)]

FYI, looking at these commits at least some of the apps are using the wrong applicationName. See 'Runtime Environment' in http://developer.ubuntu.com/publish/apps/security-policy-for-click-packages/ for details. In essence, if these apps move to click packages, they need to update their applicationName in the MainView {} of their QML to match that of the "name" field of the click manifest to run at all. Once that is done though, the autopilot tests will fail again because they will be looking for the files in the wrong place. I suggesting working with serguisens on what to change the applicationName to (since he has been working on packaging these as click), and then adjust the autopilot tests accordingly.

FYI, QtCreator now does all this correctly when developing new applications, so this shouldn't be a problem with new apps.