Lines Matching refs:what
70 # Rather than print STDERR "# here's what went wrong\n"
71 diag("here's what went wrong");
149 If you want to control what functions Test::More will export, you
216 The later gives you some idea of what failed. It also makes it easier
297 cannot know what you are testing for (beyond the name), but is() and
298 isnt() know what the test was and why it failed. For example this
311 So you can figure out what went wrong without rerunning the test.
408 Its advantage over ok() is when the test fails you'll know what $this
597 what went wrong when it failed. But sometimes it doesn't work out
767 there are, $why and under what $condition to skip them. An example is
848 how much work is left to be done, you're aware of what bugs there are,
914 quite sure what will happen with filehandles.