Author taleinat
Recipients Saimadhav.Heblikar, jesstess, taleinat, terry.reedy
Date 2014-06-14.12:25:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1402748710.73.0.768641789807.issue21686@psf.upfronthosting.co.za>
In-reply-to
Content
Here are details how to trigger all of the uncovered code lines and branches, listed by line.


Uncovered lines:

Line 159: This catches would-be identifiers (variable names) which are keywords or begin with a character that can't be first (e.g. a digit). We should have at least one test for each of these cases.

Lines 196-198: These strip comments from inside an expression. We should have a test with sample code with a multi-line expression with a comment inside it.

Line 225: Triggered when trying to find an expression including parentheses or brackets when they aren't closed, e.g. "[x for x in ".


Uncovered branches (except those which just cause the above):

Lines 32, 42: To trigger, have a block of code over 50 lines long and create a HyperParser at the last line (not inside any other block).

Line 236: Have a string literal inside brackets or parens, and call get_expression().
History
Date User Action Args
2014-06-14 12:25:10taleinatsetrecipients: + taleinat, terry.reedy, jesstess, Saimadhav.Heblikar
2014-06-14 12:25:10taleinatsetmessageid: <1402748710.73.0.768641789807.issue21686@psf.upfronthosting.co.za>
2014-06-14 12:25:10taleinatlinkissue21686 messages
2014-06-14 12:25:10taleinatcreate