Fix async blackd tests which won't fail currently #966
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While working on #691, I discovered that I couldn't get
blackd
tests to fail in their current form (e.g. basic sanity check asserting1 == 2
wouldn't fail the test suite).I refactor the tests for
blackd
into their ownAioHTTPTestCase
which uses abstractions documented here fromaiohttp
. Now, tests fail reliably when they are forced to fail or when there's a legit logical error.I also fix an exception that is thrown when no event loop is present in
event_loop
. Additionally, Iraise
inskip_if_exception
when an exception that shouldn't cause the test to be skipped is caught.