Open schwernbot opened 10 years ago
From: @schwern Date: Friday Apr 12, 2013 at 09:30 GMT Orig: https://github.com/Test-More/test-more/issues/352#issuecomment-16283895
While at the QA Hackathon we'll be coordinating using this Etherpad. http://openetherpad.org/8IrZW54mHd
From: @karenetheridge Date: Friday Apr 12, 2013 at 22:04 GMT Orig: https://github.com/Test-More/test-more/issues/352#issuecomment-16320117
I'm guessing you tried to install all Test-* distributions in CPAN? That's going to miss any Test::* modules in other distributions... for example I just discovered that Test::Moose fails (due to its use of ->details). I've added that to the etherpad list (and removed a false negative, Test::LWP::UserAgent, that isn't a test module on its own but fails due to its use of Test::TempDir).
i.e. dist/test_dists should test not just Test-* distributions, but also do something like what Test::DependentModules does, and test all reverse-dependencies of Test::Builder.
From: @karenetheridge Date: Tuesday Apr 16, 2013 at 19:36 GMT Orig: https://github.com/Test-More/test-more/issues/352#issuecomment-16466841
https://metacpan.org/requires/distribution/Test-Tester?sort=[[2,1]] is a good list of other distributions that ought to be tested.
From: @schwern Date: Wednesday Apr 17, 2013 at 11:26 GMT Orig: https://github.com/Test-More/test-more/issues/352#issuecomment-16500226
@karenetheridge For now we're concentrating on the Test distributions to firm up the trunk of the Test::Builder dependency tree before moving up. Many distributions fail because important Test distributions aren't working. The results are very polluted and take up time just to find out Plack isn't working because Test::TCP isn't working because Test::SharedFork isn't working which we already knew. Test::Most, Test::Class and Test::SharedFork not working knocks out a big chunk of the tree.
So keep ideas for testing the whole dependency tree on hold for now, unless you can come up with a clever way of determining where the error in a test failure lies which would be super awesome!
Checking Test-Tester deps and also Test::Builder::Tester is a good idea at this stage.
From: @karenetheridge Date: Wednesday Apr 17, 2013 at 17:50 GMT Orig: https://github.com/Test-More/test-more/issues/352#issuecomment-16521512
That's quite reasonable. My concern is mainly that there are some Test::* modules in other distributions, that might also be breaking that we don't know about. (I noticed this while trying to install Test::TempDir, which uses Moose, and Moose contains Test::Moose, which was broken.)
From: @schwern Date: Thursday Apr 11, 2013 at 00:58 GMT Orig: https://github.com/Test-More/test-more/issues/352
As of 63606c6f28e15d48a801a9572576fef0beea46e8 this is the list of Test-* distributions whose tests have been broken by Test::Builder 1.5. 104 out of 722 distributions are broken.
A test is "broken" if it passes with stable and fails with the latest Test::Builder 1.5.
They mostly fall into these categories...
There's a wiki page with more information.
To help...
Running against the Test-Builder1.5 branch...
git checkout Test-Builder1.5
export PERL5LIB=~/devel/Test-Simple/lib/
At that point you can...
Or if it works now...
Or if the problem is over your head...