On Fri, 2010-09-24, Greg Stein wrote: > On Fri, Sep 24, 2010 at 11:16, Julian Foad <julian.f...@wandisco.com> wrote: > >... > > I think we should produce a test framework that can give us a WC > > containing all the different possible WC states. Then we can write > > tests against this framework, some tests that test specific state, and > > other tests that apply the same operations to all the states and check > > that it works in all the states that it should. > > This requires a manual process of thinking of all states and all > permutations. I don't trust it.
This kind of testing is more about checking that the design is implemented and that the code paths are exercised ... > If we could somehow capture working copies from during normal test > runs, *then* I think we'd have "everything". We can easily get the > terminal state for each test, which is a great first step. It would be > great if we could also get the intermediate steps. ... while this kind is more about checking for regression or unwanted changes of behaviour. The two approaches are complementary. > Haven't thought much about it, but my thoughts were somewhere along that line. > > I have been thinking this for a while. As yet I've just got a > > rudimentary constructor for a WC containing (nearly) all *base* states. > > Not changes, yet. Here it is: > > Not sure if it solves everything, but it is a good start. Review below: Thanks for the review comments. All useful. - Julian
