README

Quick summary

Visual front-end for the LiveOps Configuration API.

Current Build Status

Version

3.1.9

How do I get set up?

1. Clone the repository
2. From the root directory of the repo, run the following command: npm install && bower install
3. Run gulp serve to start the application

_{For API development, configurator must be set up according to this article}

Note: To configure the API end-point, you can change the app/env.js apiHostname.

How do I make a new release?

Click Here

How do I feature flag?

Feature flags in config-ui are set up via an angular module that exports a constant.

To add a feature flag, go to gulp/flags.js and add your flag. It is probably best to include a default value as well. then when you do gulp build or gulp serve, add your command line arguements. For example:

$ gulp serve --outboundPages=true

.pipe($.ngConstant({
  name: 'liveopsConfigPanel.flags',
  constants: {
    appFlags: {
      OUTBOUND_PAGES: argv.outboundPages || 'Test'
    }
  }
}))

Unit tests

Run all unit tests

$ gulp test

Run unit tests and generate coverage report (view report at /coverage/PhantomJS [version]/index.html)

$ gulp coverage

Run a single spec file

$ gulp test:single --specFile="path/to/file.spec.js"

E2E tests

Login uses params.login in the respective config file and is default to titan@liveops.com Do not run the suite on a shared API as many records are created and edited. Tests depend on availability of Mailinator and expect that invitation emails are redirected to titantest@mailinator.com E2E Tests do not cover the following:

• Media Upload
• Flow designer
• Reporting Dashboards
• All browser support
• Links to external pages (Help Docs)
• Interaction with Toolbar or other components

Run all suites locally (uses config at /protractor.local.conf.js)

$ ./e2e_local.sh

Run all suites on saucelabs (uses config at /protractor.conf.js)

$ ./e2e_sauce.sh <SAUCE_USERNAME> <SAUCE_ACCESS_KEY> <SAUCE_TUNNEL>