On Mon, Jun 11, 2012 at 09:48:43PM +0200, Slaven Rezic wrote: > Steffen Schwigon <steffen.schwi...@amd.com> writes: > > Is there something else I could do with such long running test suites?
Make sure that there's some output, or spit out a warning at the beginning of the time-consuming test file, so that testers can see that it hasn't just hung. > Chance of all tests passing for Tapper-MCP's dependencies is: > > 1.8% > > (According to > http://deps.cpantesters.org/?module=Tapper%3A%3AMCP&perl=any+version&os=any+OS > ) If you specify 'any version' of perl then it assumes that you mean 5.005 for the purposes of figuring out what's in core, so many of those dependencies won't actually be dependencies on a more modern perl, and it will include test failures on very old perls too. That figure doesn't mean very much anyway: http://deps.cpantesters.org/static/overall-chance.html Proc::ProcessTable is the biggest culprit, and is likely to be quite platform-dependent. The next biggest is String::Diff, which you may be able to get rid of. Finally, the biggest cause of things not getting tested is if they require some external setup (a database, for example, or an environment variable) or there's a non-perl dependency such as on a library or an application. -- David Cantrell | A machine for turning tea into grumpiness Us Germans take our humour very seriously -- German cultural attache talking to the Today Programme, about the German supposed lack of a sense of humour, 29 Aug 2001
