linkedin/dustjs — pull request #128 by zzen (2012-08-28 18:51:45+00:00)
Title: Updated README for consistency and readability

I've updated the test README a bit since I was struggling with getting started with tests. The formatting on Github was quite broken. I feel the README still needs some work, but I need some guidance, so here are questions for discussion:

* "Dust core unit-tests" vs "Dust unit-tests using jasmine"
Are these running the same test suite, only one in node and the other in browser via jasmine? Or do the suites differ in content? (Misleading that one is called "core unit-tests" and the other "unit tests using jasmine"

* `node test/server.js` vs `node test/jasmine-test/server/specRunner.js` vs `make test` vs `make jasmine`
What is the difference between these two styles of calling node.js tests? Does one cover just core and the other full test suite? Are they identical? Why list all four?!

* can we move cover to Makefile aswell?
Reason: the recommended node.js practice is NOT to install global packages for project-specific development. Since `cover` is already listed as a dependency and thus installed via `npm install`, you can already run it via `./node_modules/.bin/cover` - and there's no need installing it again into global namespace. However, the path is a bit cumbersome, so I propose making `make cover` and `make cover-help` or just dropping these intructions in favour of existing umbrella `make coverage` (but fixing the path to be local).

* finally an almost identical README is duplicated in linkedin/dust-helpers - could the helpers perhaps just point to this README? Keeping them synchronized will be annoying.