pablogsal / pegen

84%

master: 84%

LAST BUILD ON BRANCH xfail

branch: xfail

CHANGE BRANCH

x

Reset

• xfail
• add_left_recursion_tests
• allow_to_compile_extension
• assignment
• badge
• better_errors
• better_fstrings
• ci
• compiler_error
• cov_badge
• cpegen_improvements
• curly_stuff
• cut_in_c_parser
• debug_version
• debug_version_test
• errors
• first_sets
• fix
• fix_mutual_left_recursion
• fix_mypy
• fix_refcount
• fix_script
• fix_segfault
• fix_test_parse_directory
• fix_visualizer
• format
• fstrings
• headers
• lambdadefs
• master
• metaparser
• metas
• minor_cleanups
• move_stuff
• mutual
• mypy
• new_test_structure
• number_test
• numbers
• pep7
• refactor
• refactor_string
• remove_panic
• rules_to_grammar
• segfault
• smoke_test_c_parser
• strings
• test_cparser
• visitor_Refactor

Build # 220

Build Type

push

travis-ci

Committed by pablogsal

Commit Message

Don't use xfail for failure scenarios

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.

Run Details

1562 of 1866 relevant lines covered (83.71%)

0.84 hits per line