Lines Matching +refs:view +refs:todo
26 skip todo todo_skip
960 but will work in the future (a todo test).
962 For more details on the mechanics of skip and todo tests see
966 block of tests which can be skipped over or made todo. It's best if I
1060 With a todo block, the tests inside are expected to fail. Test::More
1062 they are "todo". Test::Harness will interpret failures as being ok.
1064 You then know the thing you had todo is done and can remove the
1067 The nice part about todo tests, as opposed to simply commenting out a
1068 block of tests, is it's like having a programmatic todo list. You know
1072 Once a todo test starts succeeding, simply move it outside the block.
1087 With todo tests, it's best to have the tests actually run. That way
1094 tests will be marked as failing but todo. Test::Harness will
1493 no_plan and todo depend on new Test::Harness features and fixes. If
1494 you're going to distribute tests that use no_plan or todo your
1555 See F<http://rt.cpan.org> to report and view bugs.