Closed pauljt closed 10 years ago
I agree, lots of stuff sitting around!
I looked, briefly, for some code coverage tools and found a few but they were a little difficult to run. I might see if they plug in easily to our testing framework we have now.
I think this might as well merge into issue #1. Once we have module loading, we have clearer code dependencies. Then we can remove all those files that the libraries brought with them (like their tests and READMEs).
Should we consider this fixed with #104?
We have a lot of cruft that needs cleaning (esp. under /js/lib/). Lets clean it up and just keep the files that are actually used.