On 23/09/06, A. Pagaltzis <[EMAIL PROTECTED]> wrote:
* David Golden <[EMAIL PROTECTED]> [2006-09-17 18:10]:
> TODO means "don't have the result of this test affect the
> outcome yet".
Exactly. I think it's just the fact that it's called TODO which
leads people on a garden path.
It's partly the name and partly the very clear doumentation :)
Seriously, read it. Particularly the bit about "SKIP vs TODO".
They want to assign meaning to it
that doesn't exist, because they have a concept of what "todo
item" means. Maybe it should have been called PRETEND_OK. That
focusses on what the directive *does*, instead of what it's for.
Using it *for* some purpose would then be a matter of personal
interpretation.
Sounds good, and if there are any PRETEND_OKs in the output then
Test::Harness could say
...
t/string..........ok
All tests successful (but at least one part of this module probably
won't work for you).
Files=34, Tests=1059, 6 wallclock secs ( 4.93 cusr + 0.88 csys = 5.81 CPU)
At least then the user knows there's a problem _before_ he <insert
misfortune caused by non-functioning module>. Remember, this thread is
about how the toolchain is really for the user's benefit. Hiding
failures to avoid reports about known bugs is for the developer's
benefit, not the user,
F
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
