Lines Matching full:tests

16 prove - Run tests through a TAP harness.
27  -l,  --lib             Add 'lib' to the path for your tests (-Ilib).
29                         your tests
30  -s,  --shuffle         Run the tests in random order.
37  -f,  --failures        Show failed tests.
42       --reverse         Run the tests in reverse order.
43  -q,  --quiet           Suppress some test output while running tests.
65  -e,  --exec            Interpreter to run the tests ('' for compiled
66                         tests.)
67       --ext             Set the extension for tests (default '.t')
99 If you have a list of tests (or URLs, or anything else you want to test) in a
100 file, you can add them to your tests by using a '-':
123 If the tests fail C<prove> will exit with non-zero status.
125 =head2 Arguments to Tests
127 It is possible to supply arguments to tests. To do so separate them from
133 When running multiple tests they will each receive the same arguments.
137 Normally you can just pass a list of Perl tests and the harness will know how
138 to execute them.  However, if your tests are not written in Perl or if you
139 want all tests invoked exactly the same way, use the C<-e>, or C<--exec>
154 display any diagnostics your tests emit on STDERR.
169 select and/or order the tests to be run based on that saved state.
178 Run the same tests as the last time the state was saved. This makes it
181     # Run all tests in random order
189 Run only the tests that failed on the last run.
191     # Run all tests
197 If you also specify the C<save> option newly passing tests will be
205 Run only the passed tests from last time. Useful to make sure that no
210 Run all tests in normal order. Multiple options may be specified, so to
211 run all tests with the failures from last time first:
217 Run the tests that most recently failed first. The last failure time of
218 each test is stored. The C<hot> option causes tests to be run in most-recent-
223 Tests that have never failed will not be selected. To run all tests with
234 Run any tests with todos.
238 Run the tests in slowest to fastest order. This is useful in conjunction
239 with the C<-j> parallel testing switch to ensure that your slowest tests
246 Run test tests in fastest to slowest order.
250 Run the tests in newest to oldest order based on the modification times
255 Run the tests in oldest to newest order.
274 The C<--rules> option is used to control which tests are run sequentially and
278 The most practical use is likely to specify that some tests are not
287     # All tests are allowed to run in parallel, except those starting with "p"
290     # All tests must run in sequence except those starting with "p", which should be run parallel
297 =item * By default, all tests are eligible to be run in parallel. Specifying any of your own rules removes this one.
303 =item * The existence of a rule does not imply selecting a test. You must still specify the tests to run.
305 =item * Specifying a rule to allow tests to run in parallel does not make them run in parallel. You still need specify the number of parallel C<jobs> in your Harness object.
330 runs prove" and "options passed to the perl which runs tests"; this