Update to support multiple browsers in CI tests

- Add support for running IE and Firefox
- Update to use build-prod for testing against
- Update the prod config.js to use the sandbox by default. It's not used in
the charm deploys and is safe for us to change the default behaviour of
without issue.
- Update the process doc since we've tweaked the prod config.js settings.
- Make the test running verbose in sauce tests to aid in tracking and
debugging.
- Update browsers we run against to be the latest firefox and current sauce
supported windows.
Merge pull request #38 from mitechie/multi-browser

- Add to ci-check sequential browser runs of Firefox and IE.
- Update the version of Firefox to 25, the latest supported by saucelabs
- Update the Windows running IE due to the compatibility info on Saucelabs:
- Update to use build-prod for testing against
- Update the prod config.js to use the sandbox by default. It's not used in
the charm deploys and is safe for us to change the default behaviour of
without issue.
- Update the process doc since we've tweaked the prod config.js settings.
- Make the test running verbose in sauce tests to aid in tracking and
debugging.


https://saucelabs.com/platforms
Inspector relations tab now shows the units involved in the relation error
Fixing juju-info relations for non-subordinates.
Fixing juju-info relations for non-subordinates.

Responding to reviews: added tests, comments; clarified code.
Merge branch 'sub-rel-1259720' of github.com:makyo/juju-gui into sub-rel-1259720

Conflicts:
	app/views/utils.js
Merge pull request #39 from makyo/sub-rel-1259720

Subordinate relations were constructed too naively: juju-info is not the only indicator of a subordinate relation.
Update to run unit tests via selenium.

- Update to move the unit tests to their own function test file.
- Update to provide for allowing port specification so that tests can be run
  on specified ports to avoid collisions and make for predictable urls.
- Fix failing IE tests
- Fix the setting up of the json loading paths to work in IE since it didn't
  support location.origin.
- Provide a new makefile target for the unit tests to be started, run, and
  marked as failing/not.
- Update the ci-check to run the unit tests.
- Begin to update the browser-testing docs for the way we're currently looking
  to run them with example commands.
Merge pull request #40 from mitechie/selenium-unit-tests

- Update to move the unit tests to their own function test file.
- Update to provide for allowing port specification so that tests can be run
  on specified ports to avoid collisions and make for predictable urls.
- Fix failing IE tests
- Fix the setting up of the json loading paths to work in IE since it didn't
  support location.origin.
- Provide a new makefile target for the unit tests to be started, run, and
  marked as failing/not.
- Update the ci-check to run the unit tests.
- Begin to update the browser-testing docs for the way we're currently looking
  to run them with example commands.
Remove killing xvfb since it can be shared.
Added unit tests for relation methods in the relation viewlet
Merge pull request #42 from mitechie/test-merge-singularity

- Currently if a test and a merge (landing) job are running on Jenkins they interfere and will not pass due to no fault of the dev.
- This is due to one of them killing the xvfb process running while the other is sharing it.
- After a pre-imp with Benji it was decided there's no harm in leaving it running currently and it's the most expedient way to getting a safer CI process into place. 

Notes:

We may want to revisit this, as noted in the docs in line, if we want to do things like snapshot images in case of a failing test, etc. We can then make the xvfb port configurable as part of that work.

QA
-----

Note that below we have failed test and merge runs. I've updated the branch to remove the failing test and it's ready for review.
Added additional comments for clarity
Merge pull request #43 from hatched/relation-unit-errors

This branch adds the units in error to the relation tab in the inspector. There are only unit tests because the timings are unreliable for a purely js test and would require a settimeout/polling. It would be better tested using selenium.

To QA:
deploy mysql & wordpress
relate them
scale one to 100 units with the simulator on and then switch to the relations tab
once there is a unit in relation error it will show up in the list.
scale it down to 1 unit and switch back to the relations tab quickly you should notice it dissappear.