Skip Menu |

This queue is for tickets about the Test-POE-Client-TCP CPAN distribution.

Report information
The Basics
Id: 50800
Status: resolved
Worked: 15 min
Priority: 0/
Queue: Test-POE-Client-TCP

People
Owner: BINGOS [...] cpan.org
Requestors: bdonlan [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 1.04
Fixed in: (no value)



Subject: Tests fail - not enough tests planned
The test plans for a number of the tests list too few tests: Test Summary Report ------------------- t/01_spawn.t (Wstat: 65280 Tests: 12 Failed: 1) Failed test: 12 Non-zero exit status: 255 Parse errors: Bad plan. You planned 11 tests but ran 12. t/04_multiple.t (Wstat: 65280 Tests: 21 Failed: 2) Failed tests: 20-21 Non-zero exit status: 255 Parse errors: Bad plan. You planned 19 tests but ran 21. t/05_subclass.t (Wstat: 65280 Tests: 12 Failed: 1) Failed test: 12 Non-zero exit status: 255 Parse errors: Bad plan. You planned 11 tests but ran 12. t/07_synopsis.t (Wstat: 65280 Tests: 16 Failed: 1) Failed test: 16 Non-zero exit status: 255 Parse errors: Bad plan. You planned 15 tests but ran 16. t/08_buffer.t (Wstat: 65280 Tests: 14 Failed: 1) Failed test: 14 Non-zero exit status: 255 Parse errors: Bad plan. You planned 13 tests but ran 14. t/09_autoconnect.t (Wstat: 65280 Tests: 11 Failed: 1) Failed test: 11 Non-zero exit status: 255 Parse errors: Bad plan. You planned 10 tests but ran 11. t/09_server_info.t (Wstat: 65280 Tests: 22 Failed: 1) Failed test: 22 Non-zero exit status: 255 Parse errors: Bad plan. You planned 21 tests but ran 22. t/10_prefix.t (Wstat: 65280 Tests: 16 Failed: 1) Failed test: 16 Non-zero exit status: 255 Parse errors: Bad plan. You planned 15 tests but ran 16. Files=14, Tests=147, 5 wallclock secs ( 0.25 usr 0.04 sys + 4.08 cusr 0.73 csys = 5.10 CPU) Result: FAIL Failed 8/14 test programs. 9/147 subtests failed. Raw output from one of the tests: ] perl -Ilib t/01_spawn.t 1..11 ok 1 - use Test::POE::Client::TCP; ok 2 - The object isa Test::POE::Client::TCP ok 3 - testc_registered ok 4 - The object isa Test::POE::Client::TCP ok 5 - testc_connected ok 6 - The object isa POE::Wheel::ReadWrite ok 7 - testc_flushed ok 8 - Got input from client ok 9 - Got something back from the server ok 10 - Hello, is it me you are looking for? ok 11 - Client disconnected ok 12 - testc_disconnected # Looks like you planned 11 tests but ran 12.
Sorry, yes, this turned out to be a regression in POE.

1.06  Mon Oct 26 23:22:03 GMT 2009
  - Amended tests and bumped required POE version
Thanks for the ticket.