On Thu, Dec 5, 2013 at 9:20 AM, Edward K. Ream <[email protected]> wrote:
An Aha: Leo's bzr log provides the ultimate test bed. We "mine" the bzr > log for diffs. These diffs include sentinels, so they show the *optimal* > operation of @shadow. Stripping sentinels from the "incoming" diffs > provides the input to the @shadow algorithm. We can then compare the > output of @shadow with the actual diffs. In other words, the contents of > the bzr log provide the foundation for a huge unit test. > It's possible that last night's vivid dream was "really" about this idea ;-) It turns out to be rubbish, for two reasons: 1. The bzr code base is ridiculously hard to use. I never want to see it again, much less use it. 2. The idea of using the bzr commits is a feeble, very expensive, alternative to doing proper unit tests. Having thousands of tests is no guarantee that those tests actually cover the relevant cases! Most will be utterly redundant. In short, the Aha isn't. The proper way forward is simply to devise unit tests for the hard @shadow cases. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
