Hi, Stevan Little wrote: >> The idea was that t/force_todo can be deleted/cleared after a >> release, so all tests which were only force_todoed were instantly >> unTODOed. > > Unfortunately that is not how it is being used though. It sticks > around, and in some cases maybe even being used as a informal TODO > list.
true. > Although after some discussion with nothingmuch on IRC, I think I have > come to good compromise. > > We remove all the todo_ functions, and we add a named param "todo" to > all our test functions. This would allow test level TODO-ing. > > Then we add the force_todo() function, to allow for file level > TODO-ing. > > And we introduce some kind of global variable/env variable to do test > suite wide TODO-ing. > > This should give us enough granularity of control as well as make it > simple to just "flip a switch" for release. That sounds great! :) --Ingo -- Linux, the choice of a GNU | The next statement is not true. generation on a dual AMD | The previous statement is true. Athlon! |
