Skip to content

databindery/bindery-ui

Repository files navigation

bindery-ui: AngularJS Frontend for DataBindery API Platform

This code base inherits the following features from the lineman-angular-template:

  1. Template Precompilation into Angulars $templateCache using grunt-angular-templates
  2. Configured grunt-ngmin so you don't have to fully qualify angular dependencies.
  3. Auto generated sourcemaps with inlined sources via grunt-concat-sourcemap (you'll need to enable sourcemaps in Firefox/Chrome to see this)
  4. Unit Tests and End-to-End Tests
  5. Configuration to run Protractor for End-to-End Tests

Instructions

Requirements

  • node JS

Clone & Run

  1. git clone https://github.com/cocupu/bindery-ui
  2. cd bindery-ui
  3. sudo npm install -g lineman
  4. npm install
  5. bower install
  6. lineman run
  7. open your web browser to localhost:8000

Running Tests

To run the unit tests:

  1. lineman run from 1 terminal window
  2. lineman spec from another terminal window, this will launch Testem and execute specs in Chrome

To run the end-to-end tests:

  1. npm install protractor
  2. brew install selenium-server-standalone
  3. Make sure you have chrome installed.
  4. lineman run from 1 terminal window
  5. lineman grunt spec-e2e from another terminal window

Troubleshooting:

If you see this error: Warning: there's no selenium server jar at the specified location,
you may need to change the selenium-server-standalone jar version in config/spec-e2e.js
to the actual you see in /usr/local/opt/selenium-server-standalone (brew users may have a libexec directory).

If you see this error: Fatal error: The path to the driver executable must be set by the
webdriver.chrome.driver system property, you may need to download the chromedriver
(https://code.google.com/p/selenium/wiki/ChromeDriver) and place it in /usr/local/bin (mac).

Notes

Routing

Currently the code uses ui-router to handle state between pages and mappings between url and state. It seemed like a good idea at the time, but I plan to tear it out. See issue #3.