Tests are not available or not run during package build
Bug #1293467 reported by
Robie Basak
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-jujuclient |
New
|
Undecided
|
Unassigned | ||
python-jujuclient (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
python-jujuclient upstream: doesn't ship test_jujuclient.py in the PyPI source tarball that is released.
python-jujuclient in Ubuntu: does run tests as part of the package build.
Changed in python-jujuclient (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
To post a comment you must log in.
Upon further investigation, it looks like test_jujuclient.py assumes that a juju environment is set up already, and that it is on EC2:
def test_juju_ info(self) :
self.assertEqu al(
self. client. info(),
{' DefaultSeries' : 'precise',
' Name': 'iaas-stage',
' ProviderType' : 'ec2'})
I'm not sure on this, though. If the tests supported the local provider, then we could potentially run dep8 tests in a KVM environment. Better, the tests could mock out juju itself to test its own functionality.