-
-
Notifications
You must be signed in to change notification settings - Fork 70
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 property based tests #66
base: master
Are you sure you want to change the base?
Add property based tests #66
Conversation
Wow! A PR accompanied by a conference talk! I'm not going to merge this right now, but I will check out this branch and see if I can address the bugs it raises. Thank you for this! |
Hey man. Finally getting back to this. I think I may have stopped watching your talk after I'd concluded that you had a good point, but before you called out this library and PR specifically. Great job, again! The OOP nature of the test was initially very off-putting, as I have not thought in OOP in years, but I've finally got my head around it, and love how it's generating specific failing tests for me. I'll be fixing them over the coming days. This library will be immeasurably better for your contribution. |
Okay, all the issues you've linked to have been fixed/resolved. However, I don't think I can merge this PR, because it's still breaking for reasons that I think are problems with the test rather than the library. |
Thank you for resolving those issues. I hope all users of this library and users of apps build with it will now have a better experience using it. I really appreciate all the time you took to build and maintain final-form. I'll take a closer look at this test in the coming days in an attempt to make it pass. |
Hey!
First of: I know asking to add 500 LOC to an OS library is a lot.
I want you to understand well the motivation behind this change and the value of those tests.
I noticed that people reported similar issues to final-form-arrays repository, like this and this.
At the time I was researching property-based testing and decided to give it a shot.
One weekend later I was done with tests present in this PR.
Those tests found the following issues:
I explained the idea behind those tests during Frontend Con 2018. You can see this public talk here.