Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incremental Parser Stability (#103) #113

Open
StephanErb opened this issue Aug 23, 2011 · 2 comments
Open

Incremental Parser Stability (#103) #113

StephanErb opened this issue Aug 23, 2011 · 2 comments

Comments

@StephanErb
Copy link
Member

This is a bug to track progress the current list of failing incremental parser tests.

As it stands we have 74 tests of which 11 are failing.

Mind that TestParsingScenarios only checks for crashes. It should be enhanced to return a status report about deleted and created modelelements. This can be done by comparing the old an and new textblocks model.

From the perspective of testcoverage, we seem to lack tests which use alternatvies and conditionals, especially nested alternatives.

@ghost ghost assigned tgold Aug 23, 2011
@StephanErb
Copy link
Member Author

We do now have 7 failures in 83 testcases. 4 of these failures are due to a simple re-use check that asserts that the root object was not replaced by a new one. This check is as basic as it can get.

We do still lack test coverage for conditionals and alternatives. Once we have implement these and dropped some dead parser/lexer code, we can expect the branch coverage to be fairly reasonable.

@StephanErb
Copy link
Member Author

We have gone a long way but are not there yet. We are now, after merging pull request #128, down to two failing testcases. However, working within an editor shows that there seem to be more stability issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants