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

More tests #785

Merged
merged 5 commits into from Dec 18, 2016

Conversation

Projects
None yet
3 participants
@rtfeldman
Member

rtfeldman commented Dec 18, 2016

Add some more tests which also serve as regression tests for parser bugs.

@process-bot

This comment has been minimized.

Show comment
Hide comment
@process-bot

process-bot Dec 18, 2016

Thanks for the pull request! Make sure it satisfies this checklist. My human colleagues will appreciate it!

Here is what to expect next, and if anyone wants to comment, keep these things in mind.

process-bot commented Dec 18, 2016

Thanks for the pull request! Make sure it satisfies this checklist. My human colleagues will appreciate it!

Here is what to expect next, and if anyone wants to comment, keep these things in mind.

@rtfeldman rtfeldman merged commit 1642a4d into master Dec 18, 2016

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details

@rtfeldman rtfeldman deleted the more-tests branch Dec 18, 2016

@evancz

This comment has been minimized.

Show comment
Hide comment
@evancz

evancz Dec 18, 2016

Member

I think putting them in https://github.com/elm-lang/elm-compiler/tree/master/tests/test-files/good or https://github.com/elm-lang/elm-compiler/tree/master/tests/test-files/bad would be better. There is already infrastructure that is specifically about detecting code gen changes and making sure certain things parse or fail.

Member

evancz commented on a62e6d0 Dec 18, 2016

I think putting them in https://github.com/elm-lang/elm-compiler/tree/master/tests/test-files/good or https://github.com/elm-lang/elm-compiler/tree/master/tests/test-files/bad would be better. There is already infrastructure that is specifically about detecting code gen changes and making sure certain things parse or fail.

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