I'd prefer if this functionality was structured differently for a cleaner presentation.  I have a suggestion... move the CB.paths stuff to candybean side like I previously suggested, then turn this into a CandybeanTest or something like that, which becomes the abstract test for other tests to extend.  Then it becomes clear what this file is both seeing it first... and seeing it extended in downstream tests.  What you think?