magnum/magnum/tests
Dane LeBlanc dffbabcdc7 Log copy for failed functional tests cannot be disabled
Setting the following in functional_creds.conf doesn't have any effect
for failed functional container tests:
    copy_logs = False

Description of changes/issues addressed:
- Client functional tests look in functional_creds.conf for the
  copy_logs setting while tempest/api tests look in tempest.conf.
  So an accessor method 'get_copy_logs' is added for BaseMagnumTest
  (for tempest tests), and this gets overridden by BaseMagnumClient.
- Call to lamda was missing an argument in copy_logs_handler.
- set_copy_logs in config.py was setting cls.copy logs inconsistently
  (sometimes boolean True, otherwise to a string).
- BaseMagnumClient was calling bool() on a string: "bool(copy_logs)".
  bool() on a string always returns True except for null string.

Change-Id: I234fd0433602914fdf03f04f2394f6dc802df4fd
Closes-Bug: #1570949
2016-04-18 11:22:01 -04:00
..
contrib Merge "Functional tests should support DNS nameserver config" 2016-04-18 07:55:10 +00:00
functional Log copy for failed functional tests cannot be disabled 2016-04-18 11:22:01 -04:00
unit Merge "Add support for docker registry" 2016-04-17 15:11:32 +00:00
__init__.py Remove redundant FunctionalTest class 2015-07-15 03:39:11 +08:00
base.py Copy logs on test failure 2016-02-29 10:25:10 -06:00
conf_fixture.py Copy logs on test failure 2016-02-29 10:25:10 -06:00
fake_policy.py Remove node object from Magnum 2016-02-04 14:02:49 +08:00
fakes.py Remove duplicate X-Roles 2016-02-26 10:09:14 +08:00
policy_fixture.py Remove redundant code about fake_policy 2015-08-07 01:29:26 +00:00
utils.py Remove redundant code from magnum.test.utils 2015-07-20 21:53:12 +08:00