yes, the actual root of this problem is the choice of keeping javascript and coffeescript tests so tightly coupled. it's a choice with good and bad consequences, unfortunately i think this coupling is going to drop on the long term, since the rewriters are diverging. for example multiline doctests in javascript could require several tests.

the test list for coffee should therefore be different from the test list for java. adding a fake test in coffe can be fine as a workaround

as i wrote before, on the long term i think it would make sense to have specific tests for each rewriter, and common tests on the doctest execution function. the current tests work like unity tests for the whole project, this  was powerful until now, but if the range of supported sintaxes will grow more localised tests will be more useful