Fix backend unit tests.

Fix backend unit tests.

Make the backend unit tests not expect any extra repositories.

https://code.launchpad.net/~teknico/charms/precise/juju-gui/fix-unit-tests/+merge/167742

(do not edit description out of merge proposal)

[teknico, 2013-06-06 11:34:46]

Please take a look.

[frankban, 2013-06-06 12:10:44]

LGTM, with a request and a suggestion:

- please increase the charm revision number;
- re backend.repositories, maybe compare them with an empty set (if that's the
actual result) instead of False?

Thank you.

[teknico, 2013-06-06 13:20:28]

frankban wrote:
> LGTM, with a request and a suggestion:
> 
> - please increase the charm revision number;

Right, I keep forgetting that.


> - re backend.repositories, maybe compare them with an empty set
>   (if that's the actual result) instead of False?

Well, would it improve matters? In Python it's idiomatic for the False value to
mean "empty" for collections. The test would then mistakenly fail for, say,
empty sequences, if one day we switch away from sets.

[bac, 2013-06-06 13:46:38]

LGTM.  I also like Francesco's suggestion about comparing for an empty set even
with the risk up having to update the test should we change in the future.

[teknico, 2013-06-06 13:55:45]

*** Submitted:

Fix backend unit tests.

Make the backend unit tests not expect any extra repositories.

R=frankban, bac
CC=
https://codereview.appspot.com/10020044