Re^3: Debugging DBI placeholders

I've no idea, I wrote it but do not decide what gets into ActiveState. It is a pure Perl module so should be easy to install even without a ppm.

Comment on Re^3: Debugging DBI placeholders

Replies are listed 'Best First'.
Re^4: Debugging DBI placeholders by VinsWorldcom (Prior) on Feb 04, 2011 at 20:18 UTC
Your tests are too detailed for the automated Activestate build process. I had that problem too. http://ppm4.activestate.com/MSWin32-x86/5.12/1200/M/MJ/MJEVANS/DBIx-Log4perl-0.23.d/log-20101013T212740.txt 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.	[reply]

Replies are listed 'Best First'.

Re^4: Debugging DBI placeholders
by VinsWorldcom (Prior) on Feb 04, 2011 at 20:18 UTC

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

http://ppm4.activestate.com/MSWin32-x86/5.12/1200/M/MJ/MJEVANS/DBIx-Log4perl-0.23.d/log-20101013T212740.txt

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.

[reply]