Strategies for push/merge problem?

Peter Arrenbrecht peter.arrenbrecht at gmail.com
Wed Jul 16 07:08:23 CDT 2008


On Wed, Jul 16, 2008 at 1:29 PM, Peter Arrenbrecht
<peter.arrenbrecht at gmail.com> wrote:
> On Wed, Jul 16, 2008 at 10:31 AM, Adrian Buehlmann <adrian at cadifra.com> wrote:
>> Ha! On second thought it's even simpler than that.
>>
>> If you create a test that is expected to fail, then the test is a negative
>> one, which means that test is actually only successful iff and only if it
>> fails. So the test *is* successful if it fails.
>>
>> As soon as you have finished your feature, your expectation about that
>> test changes. You then expect that test to pass. Then you have to change
>> that test into a positive one. Do that in the same cset in which you
>> expect your new feature to pass your test and you have upheld the invariant.
>
> Now this I find a very interesting thought.

We once tweaked a particular testing framework so we could have pass,
fail, and /known but for the moment accepted bug/. This latter one
seems appropriate for such test-first commits, too.
-parren


More information about the Mercurial mailing list