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.

Sign up for GitHub

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

Jump to bottom

Introduce no_fnmatch_line/no_re_match_line in pytester #5914

Merged
merged 2 commits into from Oct 6, 2019
Merged

Introduce no_fnmatch_line/no_re_match_line in pytester #5914

merged 2 commits into from Oct 6, 2019

Commits on Oct 6, 2019

  1. Introduce no_fnmatch_line/no_re_match_line in pytester 

    The current idiom is to use:

  assert re.match(pat, result.stdout.str())

Or

  assert line in result.stdout.str()

But this does not really give good results when it fails.

Those new functions produce similar output to ther other match lines functions.
    @nicoddemus
    nicoddemus committed Oct 6, 2019
    Copy the full SHA
    0c18e24 View commit details
    Browse the repository at this point in the history

  2. Use new no-match functions to replace previous idiom

    @nicoddemus
    nicoddemus committed Oct 6, 2019
    Copy the full SHA
    47c2091 View commit details
    Browse the repository at this point in the history