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

Tests: Make assertCapturedSuccess check stderr is empty again #1087

Merged
merged 1 commit into from
Oct 1, 2020

Conversation

edmorley
Copy link
Member

@edmorley edmorley commented Oct 1, 2020

assertCapturedSuccess used to check that stderr was empty, until:
797652a#diff-65c067a6f0a3aef292fb54ec21a1fe8cR98

Adding back the assertion exposes some new bugs, which I'll fix in later PRs. In the meantime affected tests have been adjusted to use a new assertCapturedSuccessWithStdErr.

The test harness output for the failing case has also been improved, to ease debugging.

Closes W-7918492.
Closes #1025.

[skip changelog]

`assertCapturedSuccess` used to check that `stderr` was empty, until:
797652a#diff-65c067a6f0a3aef292fb54ec21a1fe8cR98

Adding back the assertion exposes some new bugs, which I'll fix in
later PRs. In the meantime affected tests have been adjusted to use
a new `assertCapturedSuccessWithStdErr`.

The test harness output for the failing case has also been improved,
to ease debugging.

Closes @W-7918492@.

[skip changelog]
@edmorley edmorley self-assigned this Oct 1, 2020
@edmorley
Copy link
Member Author

edmorley commented Oct 1, 2020

(This change means the tests now catch a few failure cases which would otherwise have been silently introduced once #968 is updated/merged)

@edmorley edmorley marked this pull request as ready for review October 1, 2020 16:10
@edmorley edmorley requested a review from a team as a code owner October 1, 2020 16:10
@edmorley edmorley merged commit ff8945c into main Oct 1, 2020
@edmorley edmorley deleted the fix-assertCapturedSuccess branch October 1, 2020 16:29
dryan pushed a commit to dryan/heroku-buildpack-python that referenced this pull request Nov 19, 2020
…#1087)

`assertCapturedSuccess` used to check that `stderr` was empty, until:
heroku@797652a#diff-65c067a6f0a3aef292fb54ec21a1fe8cR98

Adding back the assertion exposes some new bugs, which I'll fix in
later PRs. In the meantime affected tests have been adjusted to use
a new `assertCapturedSuccessWithStdErr`.

The test harness output for the failing case has also been improved,
to ease debugging.

Closes @W-7918492@.

[skip changelog]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

assertCapturedSuccess no longer asserts that STDERR is empty
2 participants