Add some hawt tests! /cc @jeffjewiss Please give a status update on this when you get a chance.
Yeah, I'm going to look into setting up a grunt task that generates test coverage based on tests for lines of code in the DSS lib. I'll keep you posted.
Can you propose a workflow for this? Like which libraries we'll use (ie. node unit and jasmine) and what you think would be valuable to be tested (just to outline some goals). And can you open a branch on the repo itself instead of your fork? Not sure if that makes more sense then working in your fork but it would be nice to have it all in one place. Let me know your thoughts :)
I think unit tests are going to be a lot easier now that the parser lives separately from the grunt-task. It's going to be valuable to have both well vetted and tested, but in either case, we're dealing with different concerns. @jeffjewiss let me know your thoughts on the best suite of tools specifically for testing the parser.
Note: I've currently removed Travis CI for this repo until we get a chance to sync in person about this.