Hi,
I was surprised by how the cover-omit/include-paths work.
I was hoping that cover-include-paths would be the the winner if some file is both in omit and include, but if I understand the code correctly it seems that includes are just ignored.
Next I was hoping that defining cover-omit-paths would replace the test-omit-paths but it seems they are on top of the test-omit-paths.
If the above is the intended behavior, could it be explained better in the documentation?
My current setup:
- My lib has a separate tests directory
- My info.rkt file has a
test-omit-paths that omits everything except the main file and the test files, and a test-include-paths that explicitly includes the "tests" directory.
- This setup leads to
cover showing "100%" on all my test files, but not telling me anything about the files actually tested.
What would be the best way forward for me with this setup?
Hi,
I was surprised by how the cover-omit/include-paths work.
I was hoping that
cover-include-pathswould be the the winner if some file is both inomitandinclude, but if I understand the code correctly it seems thatincludesare just ignored.Next I was hoping that defining
cover-omit-pathswould replace thetest-omit-pathsbut it seems they are on top of thetest-omit-paths.If the above is the intended behavior, could it be explained better in the documentation?
My current setup:
test-omit-pathsthat omits everything except the main file and the test files, and atest-include-pathsthat explicitly includes the "tests" directory.covershowing "100%" on all my test files, but not telling me anything about the files actually tested.What would be the best way forward for me with this setup?