The good features only being in the commercial version is a bit of a problem. We might put testable properties into the CouchDb source code, which don't affect anyone's ability to compile and run the code; but anyone who has QuickCheck can, in addition to the eunit tests, also run QuickCheck tests. In particular, a collaboration with Quvik might involve them undertaking to run the tests before each release.
It's not quite as straightforward as that, because we'd have to have dummy versions of their macros to ensure that compilation works for the large majority of people without QuickCheck, but you see the idea. However, I'm not sure if the general scheme fits well with the Apache philosophy. Nick On 13 October 2014 13:41, Alexander Shorin <[email protected]> wrote: > On Mon, Oct 13, 2014 at 4:26 PM, Nick North <[email protected]> wrote: > > As they have now looked at CouchDb themselves, maybe there could be some > > collaboration with them to create a larger QuickCheck test suite? > > That would be cool on one hand. On the other, the most interesting > features are provided with commercial version. I'm not sure that we'll > be able to include it into our test suite. > > As for the features that are available in free version, with some > additional work we can setup same fuzzy testing suite on top of the > same eunit. It will be stupid and primitive, for sure, but simple. QC > has a problem that without reading the docs and having some experience > with it would be hard to write any test or understand what's going on > there. Too high intro level may not encourage people to write tests > for their contributions. > > Regardless the my pessimistic response, I think this would be great > experience in anyway (: > > -- > ,,,^..^,,, >
