SPT: parse error in test is not reported at the test
If you create a test, for example like
test foo [[ long x ]] run debug to Program(_, _)
Note that in this C-language example the semicolon is omitted, hence a parse error in this test.
spoofax will generate an error:
Analysis failed Stratego stack trace: editor_analyze_0_0 editor_analyze_0_0 scope_paths_1_2 dr_scope_1_1 dr_scope_1_1 collect_all_2_0 foldr_3_0 foldr_3_0 check_error_0_0at the very top of the SPT file.
Instead, it should mark the test as a failure with a message like parse failure.Submitted by Arian on 30 November 2015 at 20:46
Does it report a parse error if the test expectation is
parse to ...it works correctly.
That fragment doesn’t parse (since recovery is off in SPT), which produces a null parse result, which probably breaks the run test expectation. It should test if the parse result is null and show parse errors instead.
Log in to post comments