You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that there is a bug with bisect_ppx in our internal project, as some expect_tests are not being captured.
However, when I change some of the expected test case, make it trigger some diff, such as changing from 3 to 4:
And run the following command:
dune runtest --instrument-with bisect_ppx --force
bisect-ppx-report html
open _coverage/index.html
And it just been covered!
Just wondering if anything I'd missed?
PS
In order to verify if the bisect_ppx has the expect_test test bug, I have created a demo repository that basically mirrors the our internal project structure. It appears to work in the expect_test cases. For example:
❯ tree cl
cl
├── dune
├── in101.ml
└── test
├── dune
└── intest.ml
By running the following commands, we can achieve 100% coverage:
❯ rm -rf _build;rm -rf _coverage
❯ dune runtest --instrument-with bisect_ppx --force
We come in peace.
❯ bisect-ppx-report html
❯ open _coverage/index.html
The text was updated successfully, but these errors were encountered:
In order to verify if the bisect_ppx has the expect_test test bug, I have created a demo repository that basically mirrors the our internal project structure. It appears to work in the expect_test cases. For example:
Does this project reproduce the bug? From this text, I got the impression that when you tried to reproduce the bug in a smaller project, everything worked.
@liweijian I may have a related issue. Would you mind having a look at #411 and let me know if BISECT_FILE does anything for you? I'm preparing to use bisect_ppx more and would be grateful for any insights into the setup. Thanks!
It seems that there is a bug with bisect_ppx in our internal project, as some expect_tests are not being captured.
However, when I change some of the expected test case, make it trigger some diff, such as changing from
3
to4
:And run the following command:
And it just been covered!
Just wondering if anything I'd missed?
PS
In order to verify if the bisect_ppx has the expect_test test bug, I have created a demo repository that basically mirrors the our internal project structure. It appears to work in the expect_test cases. For example:
Contents of
cl/dune
:Contents of
cl/in101.ml
:Contents of
cl/test/dune
:Contents of
cl/test/intest.ml
:By running the following commands, we can achieve 100% coverage:
The text was updated successfully, but these errors were encountered: