In this project I use:

Application skeleton (angular-seed)for a typical AngularJS web app. Bootstrap framework Angular directive 'angularUtils.directives.dirPagination' for datatable pagination 'angucomplete' AngularJS Autocomplete Directive for quickly create autocomplete boxes that pull data either from a server or local variable.

The SPA contains feature:

2 Example of data searching:

Autocomplete search
Sample search & data pagination
    * Data Pagination
    * Data Sorting
    * Remove the single item in list

To get you started you can simply clone the code-challange repository and install the dependencies:

You need git to clone the code-challange repository. You can get git from http://git-scm.com/.

We also use a number of node.js tools to initialize and test code-challange. You must have node.js and its package manager (npm) installed. You can get them from http://nodejs.org/.

Clone repository using git:

git clone https://github.com/angular/code-challange.git
cd code_challange

If you just want to start a new project without the code-challange commit history then you can do:

git clone --depth=1 https://github.com/angular/code-challange.git <your-project-name>

We have 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.
• We get the angular code via bower, a client-side code package manager.

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

npm install

Behind the scenes this will also call bower install. You should find 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

Adding Bootstrap dependency

bower install bootstrap
npm install bootstrap

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

npm start

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

There are two kinds of tests in the code-challenge application: Unit tests and End to End tests.

The code-challenge app comes preconfigured with unit tests. These are written in Jasmine, which we run with the Karma Test Runner. We provide a Karma configuration file to run them.

• the configuration is found at karma.conf.js
• the unit tests are found next to the code they are testing and are named as ..._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 sit and watch the source and test files for changes and then re-run the tests whenever any of them change. 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

The code-challenge app comes with end-to-end tests, again written in Jasmine. These tests are run with the Protractor End-to-End test runner. It uses native events and has special features for Angular applications.

• the configuration is found at e2e-tests/protractor-conf.js
• the end-to-end tests are found in e2e-tests/scenarios.js

Protractor simulates interaction with our web app and verifies that the application responds correctly. Therefore, our web server needs to be serving up the application, so that Protractor can interact with it.

npm start

In addition, since Protractor is built upon WebDriver we need to install this. The code-challenge project comes with a predefined script to do this:

npm run update-webdriver

This will download and install the latest version of the stand-alone WebDriver tool.

Once you have ensured that the development web server hosting our application is up and running and WebDriver is updated, you can run the end-to-end tests using the supplied npm script:

npm run protractor

This script will execute the end-to-end tests against the application being hosted on the development server.

Travis CI is a continuous integration service, which can monitor GitHub for new commits to your repository and execute scripts such as building the app or running tests. The code-challenge project contains a Travis configuration file, .travis.yml, which will cause Travis to run your tests when you push to GitHub.

You will need to enable the integration between Travis and GitHub. See the Travis website for more instruction on how to do this.

CloudBees have provided a CI/deployment setup:

If you run this, you will get a cloned version of this repo to start working on in a private git repo, along with a CI service (in Jenkins) hosted that will run unit and end to end tests in both Firefox and Chrome.

For more information on AngularJS please check out http://angularjs.org/