On Mar 11, 2009, at 11:53 PM, Carl Witty wrote: > On Wed, Mar 11, 2009 at 11:39 PM, Stefan Behnel > <[email protected]> wrote: >> 2) Every trac ticket must have a bug test case associated with it. >> This >> means that there must be a failing test case in tests/bugs/ named >> "nicely_descriptive_name_here_Txyz.pyx" (where 'xyz' is the ticket >> number), >> or a patch in trac that adds this test case. See >> >> http://wiki.cython.org/HackerGuide >> >> Please try to do this even for the tricky cases that feel like >> there isn't >> a good test case. Reproducing a bug is critical for fixing it, and >> having a >> test case is critical for not breaking it in the future. > > Does that mean I can't report bugs to trac anymore, without > constructing a test case in the form of a Cython patch? If so, then > -0. (I probably just wouldn't bother reporting bugs any more under > such a rule.)
My interpretation is that bugs won't get assigned a release milestone without a clear testcase. This will probably impact how much it's worked on as well. The testcase does not need to be in the form of a patch (until we actually commit it). If I work on a trac ticket with an "inline" testcase, I'll probably go ahead and add it to the /tests/ bugs directory myself. > If you just mean that every patch that purports to fix a bug must also > include a test case, then +1 to that (and to the rest of your list). Yes, for sure on this point. - Robert _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
