that unit tests use. maybe there's some magic that's supposed to
automatically use those things, even though they're hidden in deeply
buried paths with no machine predictable naming scheme. I can't
imagine that these unit tests passed before unless there is/was
some magic. I hobbled this in to working with a use lib and a
use for the module, but after doing this second one of these,
I'm having serious doubts about whether I'm just spackling over
the problem.