Qucs-S S-parameter Viewer & RF Synthesis Tools
Loading...
Searching...
No Matches
Public Member Functions | List of all members
parsimonious.tests.test_expressions.ErrorReportingTests Class Reference
Inheritance diagram for parsimonious.tests.test_expressions.ErrorReportingTests:
Inheritance graph
[legend]
Collaboration diagram for parsimonious.tests.test_expressions.ErrorReportingTests:
Collaboration graph
[legend]

Public Member Functions

 test_inner_rule_succeeding (self)
 
 test_rewinding (self)
 
 test_no_named_rule_succeeding (self)
 
 test_parse_with_leftovers (self)
 
 test_favoring_named_rules (self)
 
 test_line_and_column (self)
 

Detailed Description

Tests for reporting parse errors

Member Function Documentation

◆ test_favoring_named_rules()

parsimonious.tests.test_expressions.ErrorReportingTests.test_favoring_named_rules (   self)
Named rules should be used in error messages in favor of anonymous
ones, even if those are rightward-progressing-more, and even if the
failure starts at position 0.

◆ test_inner_rule_succeeding()

parsimonious.tests.test_expressions.ErrorReportingTests.test_inner_rule_succeeding (   self)
Make sure ``parse()`` fails and blames the
rightward-progressing-most named Expression when an Expression isn't
satisfied.

Make sure ParseErrors have nice Unicode representations.

◆ test_line_and_column()

parsimonious.tests.test_expressions.ErrorReportingTests.test_line_and_column (   self)
Make sure we got the line and column computation right.

◆ test_no_named_rule_succeeding()

parsimonious.tests.test_expressions.ErrorReportingTests.test_no_named_rule_succeeding (   self)
Make sure ParseErrors have sane printable representations even if we
never succeeded in matching any named expressions.

◆ test_parse_with_leftovers()

parsimonious.tests.test_expressions.ErrorReportingTests.test_parse_with_leftovers (   self)
Make sure ``parse()`` reports where we started failing to match,
even if a partial match was successful.

◆ test_rewinding()

parsimonious.tests.test_expressions.ErrorReportingTests.test_rewinding (   self)
Make sure rewinding the stack and trying an alternative (which
progresses farther) from a higher-level rule can blame an expression
within the alternative on failure.

There's no particular reason I suspect this wouldn't work, but it's a
more real-world example than the no-alternative cases already tested.

The documentation for this class was generated from the following file: