-
Notifications
You must be signed in to change notification settings - Fork 224
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
Adds more verification tests #475
Conversation
I guess this depends on #474? |
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.
Looks great, thanks a lot @Shivani912! Let's merge this after #474
Yes :)
Thanks for an early review @romac ! Will do... |
@Shivani912 Any idea why the |
Aha, the older tests ( |
Right, this is an old test, my bad! No we don't maintain that code anymore so I guess it's fine to just comment it out until we remove that code altogether. |
Thank you @romac for actively reviewing this PR, appreciate it! I have addressed all your comments and I think it's ready to merge now. Will be great if you could approve it to be able to merge. Thanks again ! |
Great stuff, thanks @Shivani912! |
Aren't all these tests being added in the old Also, is there some way to see the mapping between the tests we have and the predicates? Like how should someone verify that there's a positive and negative test for each predicate? It would be cool to run the Go code against these as well. Is there an easy way to do that? And now that the mbt tools have landed, I guess next step is to start generating these tests from that? |
Closes #330 - I think we should close this one now as all of the predicates are being tested by conformance tests. We can open a separate issue for the lack of unit tests for these.