-
Notifications
You must be signed in to change notification settings - Fork 38
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
Add tup2 to tup9 for Gen #181
Conversation
I think these are fine. What do you think @c-cube? Even if they are so straightforward, it would be nice to include tests of them. For uniformity it would be nice to add |
can we get the same in QCheck.Gen? |
Yes I will add these in QCheck. When I did this PR I thought QCheck2 would replace QCheck. However, I started the migration in our project where we have a lot of QCheck tests and the execution's time has raised a lot. I now believe QCheck is still relevant in many cases. |
Indeed, it might be that they both have their use :-). |
Looks good I think. Thanks for the patience on such boilerplat-y code :D |
It would be great if you could extract a representable test case and share it here 🙏🙂 QCheck2 is a great effort! In the long run, I still hope for it to replace QCheck. |
It's a test in the Tezos code base, there is a lot of dependencies going on there. I don't know if it can be easily extracted for our testing purpose. |
Alternative (and easy) solution for #108.
Nothing smart happening there.