# from Paul Bennett
# on Sunday 13 June 2010 14:36:
>As you'll be able to tell (with some digging), the tests that are
> failing are one or more of the tests named
> <code>/01-try-.*/</code>. These tests are all sanity-checks put in
> place to test the underlying modules and/or libraries that my module
> itself actually relies on. Those tests don't even <code>use</code> my
> module -- they run directly on the underlying modules.
What do the underlying modules do in their tests? Are they lacking
coverage on the points you're testing there, or are their tests also
failing in the same places? Does it fail when your module code causes
the dependencies to hit these code paths?
If your distribution has tests for dependency code, either they are
redundant or should be part of the dependency's distribution.
--Eric
--
Issues of control, repair, improvement, cost, or just plain
understandability all come down strongly in favor of open source
solutions to complex problems of any sort.
--Robert G. Brown
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
