Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added support for custom response handlers to gabbi-run #95

Merged
merged 11 commits into from Oct 1, 2015
Merged

Commits on Sep 30, 2015

  1. Create basic gabbi-run test

    FND committed Sep 30, 2015
    Configuration menu
    Copy the full SHA
    587d509 View commit details
    Browse the repository at this point in the history
  2. Simplify exit interception

    FND committed Sep 30, 2015
    Configuration menu
    Copy the full SHA
    e1a09ad View commit details
    Browse the repository at this point in the history
  3. Add support for custom response handlers to gabbi-run

    with extensive assistance from @cdent
    FND committed Sep 30, 2015
    3 Configuration menu
    Copy the full SHA
    1e3cc8c View commit details
    Browse the repository at this point in the history
  4. Attempt to emit captured streams on failure

    this should make debugging a little less painful
    
    oddly, this only seems to work for STDERR - @cdent?
    FND committed Sep 30, 2015
    4 Configuration menu
    Copy the full SHA
    d93992e View commit details
    Browse the repository at this point in the history

Commits on Oct 1, 2015

  1. Configuration menu
    Copy the full SHA
    9aeca62 View commit details
    Browse the repository at this point in the history
  2. Replace dynamic with static UUID

    because why not
    FND committed Oct 1, 2015
    Configuration menu
    Copy the full SHA
    7a8aa2b View commit details
    Browse the repository at this point in the history
  3. Add shorthand for response handler extensions

    before:
    
        gabbi-run -r my_response_handler:MyResponseHandler
    
    after:
    
        gabbi-run -r my_response_handler
    
    the latter is *much* more convenient
    
    not sure where to document the contract though: the given module is
    expected to contain a `gabbi_response_handlers` object, which is either
    a sequence of response handler classes or a function returning such a
    sequence
    
    /cc @cdent
    FND committed Oct 1, 2015
    5 Configuration menu
    Copy the full SHA
    69379f2 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    ce894a6 View commit details
    Browse the repository at this point in the history
  5. Make _dump_captured in test_runner work with testr

    By default testr will swallow output to STDOUT so if we want to make
    output of gabbi-run visible when there are unexpected errors from
    runner.run() we need to send it to STDERR.
    
    (For those inclined this change can be tested by changing a test in
    test_runner to fail and then `tox -epy34 -- test_runner`.)
    cdent committed Oct 1, 2015
    Configuration menu
    Copy the full SHA
    374de34 View commit details
    Browse the repository at this point in the history
  6. Configuration menu
    Copy the full SHA
    4ac8d8e View commit details
    Browse the repository at this point in the history
  7. Replace func with meth references in docs

    not exactly sure what this means, but @cdent suggests these should be
    linked now
    FND committed Oct 1, 2015
    Configuration menu
    Copy the full SHA
    47baa65 View commit details
    Browse the repository at this point in the history