Subject: | t/content_contains.t busted with newest Test::LongString |
Hi,
The author of Test::LongString (which you are depending on) has recently
released a new version which changes diagnostics output. You can see
the change log here:
"http://cpansearch.perl.org/src/RGARCIA/Test-LongString-0.12/Changes"
Now when I try to "make test" I get the following in 't/content_contains.t':
t/content_contains.t .... 2/5
# Failed test 'Handles not finding it'
# at t/content_contains.t line 39.
# STDERR is:
# # Failed test 'Where is Mungo?'
# # at t/content_contains.t line 38.
# # searched: "<html>\x{0a} <head>\x{0a} <title>Test
Page</title>\x{0a} </h"...
# # can't find: "Mungo"
# # LCSS: "go"
# # LCSS context: "ead>\x{0a} <body>\x{0a} <h1>Test Page</h1>\x{0a}
<a href='go"
#
# not:
# /#\s+Failed\ test.*?\n?.*?at\ t\/content_contains\.t line 38.*\n?/
#
# # searched: "<html>\x{0a} <head>\x{0a} <title>Test
Page</title>\x{0a} </h"...
#
# # can't find: "Mungo"
#
# as expected
This test failure is a false positive since it's due to a change in
Test::LongString (added the LCSS and context stuff, and some other
slight reformatting).
I know you rightly might say the author of Test::LongString shouldn't
make such an incompatible change, but I can also understand why he might
think using his error messages this way is a bit out of scope. Anyway,
until we can find a solution, either backward compatibility fixes on his
part, or on some changes to this test, nobody will be able to install
the module without force.
I'm happy to help if we can coordinate what to do.
Sincerely,
John Napiorkowski (jjnapiork@cpan.org)