summaryrefslogtreecommitdiff
path: root/pod/perltodo.pod
diff options
context:
space:
mode:
authorNicholas Clark <nick@ccl4.org>2009-09-14 14:33:06 +0100
committerNicholas Clark <nick@ccl4.org>2009-09-14 14:33:06 +0100
commit5e88c5dd417b17e710ab407c5f40afe3f9de11c8 (patch)
tree2ebc8db0d963e8e28ca58e5c6f6dda5af1f0f297 /pod/perltodo.pod
parenta96d018829db6d60ab7d14d2ba51db878e944ddd (diff)
downloadperl-5e88c5dd417b17e710ab407c5f40afe3f9de11c8.tar.gz
Parallel testing is pretty much done.
Diffstat (limited to 'pod/perltodo.pod')
-rw-r--r--pod/perltodo.pod12
1 files changed, 0 insertions, 12 deletions
diff --git a/pod/perltodo.pod b/pod/perltodo.pod
index 0686853060..ec39fc9aac 100644
--- a/pod/perltodo.pod
+++ b/pod/perltodo.pod
@@ -61,18 +61,6 @@ The more practical approach, to break the task down into manageable chunks, is
to work your way though the code from bottom to top, or if necessary adding
extra C<{ ... }> blocks, and turning on strict within them.
-=head2 Parallel testing
-
-(This probably impacts much more than the core: also the Test::Harness
-and TAP::* modules on CPAN.)
-
-All of the tests in F<t/> can now be run in parallel, if C<$ENV{TEST_JOBS}>
-is set. However, tests within each directory in F<ext> and F<lib> are still
-run in series, with directories run in parallel. This is an adequate
-heuristic, but it might be possible to relax it further, and get more
-throughput. Specifically, it would be good to audit all of F<lib/*.t>, and
-make them use C<File::Temp>.
-
=head2 Make Schwern poorer
We should have tests for everything. When all the core's modules are tested,