Project

General

Profile

Support #6861

tests for valid and invalid 4GL syntax (parsing)

Added by Greg Shah almost 4 years ago. Updated 2 months ago.

Status:
New
Priority:
Normal
Assignee:
Marian Edu
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

Related issues

Related to Testing - Support #6860: lexer tests Test
Related to Conversion Tools - Feature #1757: update ANTLR to latest version New
Related to Conversion Tools - Feature #3882: changes to allow the front-end to be used for 4GL syntax checking New
Related to Testing - Support #6859: preprocessor tests Test

History

#1 Updated by Marian Edu over 3 years ago

Not sure what the plans are for this one, I would imagine really JUnit tests are to be created here for conversion so no 4GL/ABLUnit tests only sample 4GL code that will be used as conversion input... but please correct me if I'm wrong.

#2 Updated by Greg Shah over 3 years ago

#3 Updated by Greg Shah over 3 years ago

I think your idea is the correct approach.

#4 Updated by Greg Shah over 1 year ago

  • Subject changed from valid and invalid 4GL syntax (parsing) to tests for valid and invalid 4GL syntax (parsing)
  • Project changed from Conversion Tools to Testing

After considering this further, I think we need 2 approaches:

1. For valid 4GL syntax, I think we make sure that we enhance our ABLUnit tests to include everything we want to test in the parser. I don't think there is much value in having lots of parsing tests that wouldn't actually work to test the runtime behavior. Doing that might save some time on the parsing test development but it would result is a huge amount of duplication. We already need to write tests that work for all the various functional areas. They should just be used for both purposes.

2. For invalid 4GL syntax, the ABLUnit approach does not work. We will need to come up with a kind of harness or driver for running the ConversionDriver directly and checking against expected parsing/syntax failures.

#5 Updated by Greg Shah over 1 year ago

#6 Updated by Greg Shah over 1 year ago

  • Related to Feature #3882: changes to allow the front-end to be used for 4GL syntax checking added

#7 Updated by Greg Shah over 1 year ago

#8 Updated by Greg Shah 2 months ago

Documentation will be in Parser Testcases.

Also available in: Atom PDF