Lines Matching full:need
13 To start exploring some of the features of Test::Harness I need to
15 Test::Harness). For the following examples I'll also need a recent
38 I need to be careful about the include path to make sure I'm not
135 them in parallel. If I see unexpected failures I need to check my
201 If I need a feature that prove doesn't provide I can easily write my own.
241 I need to tell prove to use my My::TAP::Harness. If My::TAP::Harness
246 If I don't have My::TAP::Harness installed on @INC I need to provide
282 replace any other part of the harness. To do that I need to know
322 If I need to reach even deeper into the internals of the harness I
342 As an alternative to subclassing the components I need to change I
385 Perhaps I don't need a complete test harness. If I already have a
386 TAP test log that I need to parse all I need is TAP::Parser and the
387 various classes it depends upon. Here's the code I need to run a
407 This approach is useful if I need to convert my TAP based test