# New Ticket Created by Jerry Gay # Please include the string: [perl #56716] # in the subject line of all future correspondence about this issue. # <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=56716 >
the configure tests take too much time to run, and should be sped up by whatever means necessary so as to take a much smaller percentage of the overall time for the test suite. from the looks of it, there's a lot of setup and teardown in each step test file that requires the same code to be repeated. one example is that only a few lines of code differ between t/steps/inter_charset-01.t and t/steps/inter_charset-02.t, and mainly because there is one more test in the latter. why are all these tests being repeated? another example is that with so many files, perl is invoked many, many times. starting processes on windows is expensive, so every file (300 in t/steps and t/configure) is another invocation of perl. this adds up quickly to slow windows testing to a crawl. if instead these tests were data-driven, so the tests were in data format, and the configure system had a way to reset itself to a previous state between tests, then we could have many fewer invocations of perl--at least two orders of magnitude fewer invocations, i reckon. comments, suggestions, and questions welcome. ~jerry
