We don't really need to look for fragments that are pulled in by [% INCLUDE %] or [% PROCESS %]. While removing this code bit doesn't allow us to seperatly check that those fragments exist and compile, they'll be checked atomatically when the the template that wants them is run through the process() routine by the 004template.t test. This issue was raised because bug 98707 introduced a [% BLOCK %] element and the syntax for using that is the same as for including a template fragment.

1 files changed, 0 insertions, 15 deletions

diff --git a/t/Support/Templates.pm b/t/Support/Templates.pm
index 6e5fb2904..c15611d46 100644
--- a/t/Support/Templates.pm
+++ b/t/Support/Templates.pm
@@ -43,19 +43,4 @@ foreach my $file (@files) {
     }
 }
 
-# Now let's look at the templates and find any other templates
-# that are INCLUDEd.
-foreach my $file(@testitems) {
-    open (FILE, $include_path . "/" . $file) || next;
-    my @lines = <FILE>;
-    close (FILE);
-    foreach my $line (@lines) {
-        if ($line =~ m/\[% (?:INCLUDE|PROCESS) (.+?) /) {
-            my $template = $1;
-            push (@testitems, $template) unless $t{$template};
-            $t{$template} = 1;
-        }
-    }
-}
-
 1;