Ingo,
On Apr 21, 2005, at 10:03 AM, Ingo Blechschmidt wrote:
- Should we do away with the t/force_todo file and introduce a force_todo() function?
The idea is to move from the more centralized t/force_todo file to a more decentralized force_todo() function which would accept a list of test numbers which would be forced-TODO on a per-file basis.
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.
force_todo(1, 5, 10 .. 15, 25);
That'd be cool :)
Of course, we could make Test.pm parse sth. like the following, too. t/my_test.t 1 5 10..15 25
We could but again, we would be imposing more of a penalty on test files which dont need it.
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.
Any thoughts?
- Stevan
