Add a shebang to jshint-rhino.js to tell the shell how to execute the file and mark it executable after build. Note1: Ignore the return code of chmod in case the user is on a filesystem which does not support setting execute permission. Note2: Make use of /usr/bin/env to catch rhino anywhere in the PATH. Also reformat the rhino build target slightly to match the other targets (replace chained '&&' with separate shell commands). Combine multiple invocations of cat into one. Signed-off-by: Kevin Locke <email@example.com>
Move test files in different folders (unit, regression, helpers) and change appropriate make and readme entries.
View the parts of jshint that are covered by the tests (file by file or all test files together). Coverage analysis is done with https://github.com/coveraje/coveraje. Results are shown in the browser.
All generated files will now be placed in a `build` directory (ignored in the repo). I've also added make clean to empty `build` when needed. Renamed `env/jshint-rhino.js` to `env/rhino.js` because the 'jshint-' part seemed redundant.
* Removes load(jshint) from jshint-rhino since JSHint is included when `make rhino` is executed. * Also adds method test to Makefile which runs tests using expresso.