Go to file
Daryl Walleck aa92ff0470 Allows any valid ISO8601 timestamp in token expiry time format
* The current Tempest auth providers check for a very specific
  timestamp format for the "expires" field of token responses.
  If the Identity provider sends a response with a valid timestamp
  that does not exactly match this format, test execution is halted.
  Since the auth provider is client code, any specific functional
  checks would be better represented as a test. The client is
  primarily concerned with if the value can be parsed successfully.
  The current guidance from the API working group is that any
  valid ISO 8601 compliant timestamp should be sufficient.

  https://github.com/openstack/api-wg/blob/master/guidelines/time.rst

Change-Id: I7b8e9435b5b94a6237f300366952f6d2f6414e42
2015-06-10 14:48:51 -05:00
2014-08-27 22:52:05 -04:00
2014-08-27 22:52:05 -04:00
2014-08-27 22:52:05 -04:00
2014-08-27 22:52:05 -04:00
2014-08-27 22:52:05 -04:00
2014-08-27 22:52:05 -04:00
2014-08-27 22:52:05 -04:00
2014-08-27 22:52:05 -04:00
2014-08-28 23:00:38 -04:00
2015-02-11 19:04:47 -05:00
2015-02-09 16:22:39 +00:00
2014-12-12 22:22:14 +00:00
2015-04-15 16:17:48 +00:00

tempest-lib

OpenStack Functional Testing Library

tempest-lib is a library of common functionality that was originally in tempest (or similar in scope to tempest)

Features

Some of the current functionality exposed from the library includes:

  • OpenStack python-* client CLI testing framework
  • subunit-trace: A output filter for subunit streams. Useful in conjunction

    with calling a test runner that emits subunit

  • A unified REST Client
  • Utility functions:
    • skip_because: Skip a test because of a bug
    • find_test_caller: Perform stack introspection to find the test caller.

      common methods

Description
RETIRED, further work has moved to Debian project infrastructure
Readme 832 KiB