You need git to clone the kabaddi scheduler repository. You can get git from here.

A number of Node.js tools to are used initialize and test kabaddi scheduler. You must have Node.js and its package manager (npm) installed. You can get them from here.

There are two kinds of dependencies in this project: tools and Angular framework code. The tools help us manage and test the application.

• We get the tools we depend upon via npm, the [Node package manager][npm].
• We get the Angular code via bower, a [client-side code package manager][bower].

npm is preconfigured to automatically run bower so we can simply do:

npm install

Behind the scenes this will also call bower install. After that, you should find out that you have two new folders in your project.

• node_modules - contains the npm packages for the tools we need
• app/bower_components - contains the Angular framework files

Note that the bower_components folder would normally be installed in the root folder but kabaddi scheduler changes this location through the .bowerrc file. Putting it in the app folder makes it easier to serve the files by a web server.

The project is preconfigured with a simple development web server. The simplest way to start this server is:

npm start

Now browse to the app at localhost:8000/index.html.

The kabaddi scheduler app comes preconfigured with unit tests. These are written in [Jasmine][jasmine], which we run with the [Karma][karma] test runner. Karma configuration file is provided to run them.

• The configuration is found at karma.conf.js.
• The unit tests are found next to the code they are testing and have an _test.js suffix (e.g. match_test.js).

The easiest way to run the unit tests is to use the supplied npm script:

npm test

This script will start the Karma test runner to execute the unit tests. Moreover, Karma will start watching the source and test files for changes and then re-run the tests whenever any of them changes. This is the recommended strategy; if your unit tests are being run every time you save a file then you receive instant feedback on any changes that break the expected code functionality.

You can also ask Karma to do a single run of the tests and then exit. This is useful if you want to check that a particular version of the code is operating as expected. The project contains a predefined script to do this:

npm run test-single-run