-
Notifications
You must be signed in to change notification settings - Fork 205
Update letop-punning tests, add note to CONTRIBUTING #2748
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
Update letop-punning tests, add note to CONTRIBUTING #2748
Conversation
CONTRIBUTING.md
Outdated
| The remainder of the tests are so called "golden" or "expect" tests. These tests all consist of running `ocamlformat` on | ||
| `.ml` files and comparing the output to expected output stored in reference files. The `dune` | ||
| configuration for this is automatically generated for you based on the files present in these directories. | ||
| The most tests of `ocamlformat` are so called "golden" or "expect" tests. These |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there is a small typo here
Julow
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's really awesome ! I added some suggestions but your addition is already better than what we had before.
CONTRIBUTING.md
Outdated
|
|
||
| To add a test showing currently incorrect behavior, add a `.ml` file to | ||
| `test/failing/tests`. If command line arguments are needed, create a | ||
| corresponding `.opts` file with the same base name. The output of these tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Base name is ambiguous here, I think you should use entire file names. For example, it's not mytest.opts but mytest.ml.opts
| output to expected output stored in reference files. The `dune` configuration | ||
| for this is automatically generated for you based on the files present in these | ||
| directories. | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be useful to mention running dune runtest here. The linked "Running the Tests" section talks about several things but tests added following this guide is specifically run with dune runtest.
EmileTrotignon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The CI failures are weird and look unrelated to this PR. I think this is ready to be merged.
|
The test failures on those platforms have been coming and going on different commits, most of which are only updating the markdown, so I agree. Let me know if there is anything else needed to merge this! |
Requested by @Julow here.
This fixes up the letop-punning tests to avoid duplicating the same .ml file (and adds a
test/failingcase that I will resolve in a separate PR), and adds a section to CONTRIBUTING.md that should help others in the future get onboarded with the testing system.