Dag Sverre Seljebotn wrote: > Robert Bradshaw wrote: >> I like being able to create testfiles for specific tickets and easily >> test them, but having to move tickets back and forth between bugs and >> error/compile/run is cumbersome. Is anyone opposed to putting the >> tests directly in the appropriate test directories, and then having a >> "outstanding bugs" list in runtests.py that it uses to skip over the >> Txxx ones that are still unresolved? > > +1, though I'd like that to be a seperate unsolved.txt rather than part > of runtests.py (prettier commit history). >
I'd now prefer something slighly more ambituous though: Mark each testcase as known to fail in the testcase itself (e.g. as a comment on the first line). Going on an utopic rant: If I really had my wish without anyone spending time to implement it :-), I would actually prefer to structure all testcases in a free-form hierarchy, and instead have a header which a) indicate whether it is run/compile/error b) which ticket(s) it is related to c) module requirements d) some kind of tag system for the feature which is tested -- tags could be e.g. "IndexNode", "temps" -- Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
