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

Don't use xfail for failure scenarios (#155) #33

Merged
merged 1 commit into from Jan 15, 2020

Conversation

@sthagen
Copy link
Owner

sthagen commented Jan 15, 2020

When testing for sources that we know should raise SyntaxError we should
check explicitly that the parser raises such exception instead of
marking the cases as 'xfail'. As per the pytest docs:

A xfail means that you expect a test to fail for some reason. A common
example is a test for a feature not yet implemented, or a bug not yet
fixed.
When testing for sources that we know should raise SyntaxError we should
check explicitly that the parser raises such exception instead of
marking the cases as 'xfail'. As per the pytest docs:

    A xfail means that you expect a test to fail for some reason. A common
    example is a test for a feature not yet implemented, or a bug not yet
    fixed.
@sthagen sthagen merged commit ca0269c into sthagen:master Jan 15, 2020
1 check failed
1 check failed
Travis CI - Pull Request Build Errored
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.