This means that there will be lots of post-coding tasks that need to be performed using some other tools. For instance, automating builds, tests, deployment and execution apart from numerous other tasks like clean, copy, coverage, log, database read/write etc.
Although the task of maintaining all these software development and team activities may look daunting outside of the magical environment of a full fledged IDE like Visual Studio usually is, it is rather simple because of the packages that integrate with Node.js framework.
grunt is one such package that is similar to NAnt and Ant but has one additional advantage - it can perform, continue and wait on tasks asynchronously!
To use grunt, install it with,
> npm install grunt (-watch, contrib-execute etc)
To use mocha, use the same install method with npm.
And 'chai' adds flavor to the unit tests with the expectations and even 'promise'-s of a BDD.
Chai, too, can be installed using the npm tool.
>npm install chai
The story - watch changes to a file.
Simple steps - add the 'watch' task to the GruntFile.js as below:
Run 'grunt watch'
And every time a change is made to the source file that is being watched, the watch target will get triggered as above:
Change made to the the SQL query causes the watch target to get triggered again:
The actual rows in the DB:
and the package.json:
There are the usual caveats that you may need to reckon with like where to install the packages.
Tip: Always check the node-modules folder of your application. It should look like in the below figure:
The unit test using chai and mocha are as simple.
Execute the test using 'mocha' as:
Uncomment the 'done' lines for async callback to work seamlessly without any timeout issues related to the network or when connecting or retrieving data.
Needless to say, the unit tests wired into grunt tasks and coverage ruling the outcome of the tests and the build is ideal and this, too, is simplified now with grunt, node, mocha and blanket.
Absolutely delightful tools for Agile!