Your tests are too detailed for the automated Activestate build process. I had that problem too.

I put the simple 'does this module load' test in the t/*.t file and then made a test.pl file that required user input. The PPM autobuild process skips that part so the tests are not run but a user running the tests could respond to the prompt and run the full test suite (if they choose).

This workaround lets the modules get auto-built for Activestate PPMs (a proccess that happens automatically a few nights a week - at my best guesstimate).

See an example test.pl (borrowed heavily from Net::Telnet::Cisco) at Cisco::Management for example.