Merge lp:~clint-fewbar/pyjuju/fix-tests-with-no-ssh-key into lp:pyjuju
Proposed by
Clint Byrum
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Gustavo Niemeyer | ||||
Approved revision: | 338 | ||||
Merged at revision: | 359 | ||||
Proposed branch: | lp:~clint-fewbar/pyjuju/fix-tests-with-no-ssh-key | ||||
Merge into: | lp:pyjuju | ||||
Diff against target: |
35 lines (+5/-3) 2 files modified
ensemble/lib/testing.py (+1/-0) ensemble/providers/ec2/tests/test_provider.py (+4/-3) |
||||
To merge this branch: | bzr merge lp:~clint-fewbar/pyjuju/fix-tests-with-no-ssh-key | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Gustavo Niemeyer | Approve | ||
Review via email: mp+73849@code.launchpad.net |
Description of the change
This allows the tests to run without a pre-existing SSH key in one's home
directory. Its difficult to test the failure because you need a user with
no ssh key, even if you override HOME, because os.path.
back to using 'getent()' to find the user's home directory if HOME is
not set (hence the preservation of HOME in ensemble.
To post a comment you must log in.
Looks mostly ok, but the test is being rendered non-useful by
this change:
[1]
30 - self.env_name, {"access-key": "secret-12345"})
31 + self.env_name, config)
The original test verified that the config loaded from the environment
is the one expected. Now the serialized data is built having the
expected config at hand already, so the test that verified that it
was actually loaded from the environment is gone.