Skip to content

Latest commit

 

History

History
26 lines (17 loc) · 1.45 KB

grunt.md

File metadata and controls

26 lines (17 loc) · 1.45 KB
Raw

Back to README.md

make targets of gruntfile.js and package.json

This guide assumes, that you are familiar with the use of git, npm and grunt.

  1. git fork grunt-check-outdated plugin for grunt (https://github.com/db-developer/grunt-check-outdated.git)
  2. cd into forked grunt-check-outdated directory
  3. open a shell
  4. make sure your environment knows about the paths to nodejs
  5. run npm install

testing & coverage

The code of grunt-check-outdated can be tested. A mocha/istanbul testsuite is provided. See directory test.
Open a shell to run the tests, make sure the environment is set, cd into the forked grunt-check-outdated directory and run: grunt test

With testing (see above) code coverage is available. The results can be found in the dist/coverage folder.

building

Building can be run by grunt all and requires the build directory. After a successful build, all resulting files are located in the directory dist.

feedback

Do you feel this guide is missing essential information? Found any typos or amused by the translation? Please do not hesitate to file an issue on github!