-
Notifications
You must be signed in to change notification settings - Fork 26
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
tests for counting edges #57
tests for counting edges #57
Conversation
Awesome. Could you please rebase onto current master, so that the github action CI stuff runs on this PR. You could try and see if something like |
With #53 we won't need the |
Codecov Report
@@ Coverage Diff @@
## master #57 +/- ##
===========================================
+ Coverage 72.20% 87.26% +15.05%
===========================================
Files 1 1
Lines 421 424 +3
===========================================
+ Hits 304 370 +66
+ Misses 117 54 -63
Continue to review full report at Codecov.
|
Yes that might be true though I'm not 100% how iterators handle length 😄 |
Seems like there is a difference in the delaunay edges between Julia 1.6 and 1.7 though? 😕 |
Hm, I believe we've had changes in the random number generator between v1.6 and v1.7 or so. We should perhaps try to avoid hard-coding numbers, and instead compare two different implementations that we expect to give consistent results. |
Oh yeah that's true maybe have a file with a list of points that we can read and use those as our test case? |
We don't need a big test. Perhaps you could manually type a couple of points, say 5, at distinct locations, and then we know everything about that specific case. It is only important to step through the iterator, even if its length is short. |
True, will do |
Actually we do because we don't provide the length of the iterator at the moment. We could walk through all and count and return that though if we want to. |
Before continuing with #53 I think it would be good to have these test cases.
I assumed that the number is correct here just wanted to add a test such that we see when this changes. Not sure how to better test this.