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

Bazelify testcase/line-cont #677

Merged
merged 11 commits into from
Dec 12, 2019
Merged

Conversation

regisd
Copy link
Member

@regisd regisd commented Dec 11, 2019

No description provided.

@regisd regisd added the testing Adding tests or test infrastructure. label Dec 11, 2019
@regisd regisd requested review from lsf37 and sarowe as code owners December 11, 2019 00:40
@regisd regisd self-assigned this Dec 11, 2019
Copy link
Member

@lsf37 lsf37 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a golden file for jflex output on this one? That's the main thing this case tests in the old setup (mainly checking for equivalence of char classes and DFA)

@lsf37
Copy link
Member

lsf37 commented Dec 11, 2019

(see also the new #679)

@regisd
Copy link
Member Author

regisd commented Dec 12, 2019

Indeed, the automatic migration is for checking the golden input/output files. But this test didn't have any.

If we care about generation failure (e.g. invalid syntax in the .flex spec), or about the logs of the Jflex generation (like here), then the JflexTestRunner is the right approach.
commit 1a966d0 shows how to use it here.

@regisd regisd merged commit a35aa40 into jflex-de:master Dec 12, 2019
@regisd regisd deleted the bazelify-testcases branch December 12, 2019 21:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testing Adding tests or test infrastructure.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants