-
Notifications
You must be signed in to change notification settings - Fork 61
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
first cut at a (somewhat) useful hypothesis test #66
base: master
Are you sure you want to change the base?
Conversation
running locally gives interesting output:
so..... does that mean a glom with 50 elements resulted in a 4 second runtime? owch I wonder which one that is |
Codecov Report
@@ Coverage Diff @@
## master #66 +/- ##
==========================================
+ Coverage 94.45% 94.55% +0.09%
==========================================
Files 14 15 +1
Lines 1479 1505 +26
Branches 231 231
==========================================
+ Hits 1397 1423 +26
Misses 47 47
Partials 35 35
Continue to review full report at Codecov.
|
1 similar comment
Codecov Report
@@ Coverage Diff @@
## master #66 +/- ##
==========================================
+ Coverage 94.45% 94.55% +0.09%
==========================================
Files 14 15 +1
Lines 1479 1505 +26
Branches 231 231
==========================================
+ Hits 1397 1423 +26
Misses 47 47
Partials 35 35
Continue to review full report at Codecov.
|
I'm not sure if this is actually useful yet vs our manual testing of every possible scenario |
got an idea -- one non-trivial invariant would be ensuring that scope propagates correctly also: I'll keep building up this branch going off to the side -- the first time that it correctly identifies a new bug I'll merge to master |
No description provided.