--- Shlomi Fish <[EMAIL PROTECTED]> wrote: > This is naturally a limitation of test coverage in general which only > checks > coverage for individual code atoms, and not for all the different > paths of > execution (their Cartesian products).
Regrettably, the while code coverage is generally fairly easy to achieve, path coverage is very difficult. It's a common problem. I know of one gentleman who described his problem of having a Chain of Responsibility pattern where every step of the chain, properties stored in a database could alter the outcome. There were, at last count, 50,000 properties in the database. Code coverage was the easy bit. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/
