Looking through the click scope bugs and came across this again. I think
rather than having a keyring without a password, what we will need is a
fixture in autopilot which uses dbusmock to provide a faked keyring
service, and having all autopilot tests run under the dbusmock private
session, rather than interacting with a live system. This will allow the
tests to be run more reliably in a contained environment, when running
the tests during normal development and CI processes, and should be able
to provide a way to have the tests run against live services as well,
when we need to run things on a live device image.
** Changed in: unity-scope-click (Ubuntu)
Importance: Medium => Low
** Changed in: unity-scope-click (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-click in
Ubuntu.
https://bugs.launchpad.net/bugs/1338714
Title:
On desktop, we need a password-less keyring for autopilot tests
Status in Ubuntu CI Services:
Confirmed
Status in unity-scope-click package in Ubuntu:
Incomplete
Bug description:
When we try to add credentials to online accounts on the desktop, the
keyring dialog will be opened asking for a password. We need to find a
way to work this around.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1338714/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
