magnum/magnum/tests/functional
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
..
api Merge "Remove minion dependency on master" 2016-03-28 20:43:21 +00:00
common Log copy for failed functional tests cannot be disabled 2016-04-18 11:22:01 -04:00
k8s Use k8sclient library 2016-04-17 03:35:39 +00:00
mesos Bay test cleanup 2016-02-10 12:49:42 -05:00
swarm Functional tests should support DNS nameserver config 2016-04-15 11:39:36 -04:00
tempest_tests Functional tests should support DNS nameserver config 2016-04-15 11:39:36 -04:00
__init__.py Functional tests with Tempest - BayModel CRUD 2015-09-21 16:27:07 -05:00
python_client_base.py Log copy for failed functional tests cannot be disabled 2016-04-18 11:22:01 -04:00