-
Notifications
You must be signed in to change notification settings - Fork 137
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 an exception handler in the asyncio test runner #225
Conversation
It will now raise all the capture exceptions if the test function completes without raising any exceptions of its own. Closes #205.
tests/test_pytest_plugin.py
Outdated
result.assert_outcomes(passed=3 * len(get_all_backends()) + 1, skipped=len(get_all_backends()), | ||
failed=1) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd expect test_asyncio_exception_handler to pass, then fail in teardown:
result.assert_outcomes(passed=3 * len(get_all_backends()) + 1, skipped=len(get_all_backends()), | |
failed=1) | |
result.assert_outcomes(passed=3 * len(get_all_backends()) + 2, skipped=len(get_all_backends()), | |
failed=1) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why? The exception is raised during the actual test run (albeit in a callback), not during fixture teardown.
I'll merge this tomorrow unless you have some concerns left. |
It will now raise all the capture exceptions if the test function completes without raising any exceptions of its own.
Closes #205.