Test different browsers using the same env.

Test different browsers using the same env.

Re-deploying the charm to run tests in multiple browsers
is no longer required. Browsers can be specified as space
separated values in the environment variable 
JUJU_GUI_TEST_BROWSERS. Chrome is the default.

Note that currently only chrome tests pass.

Other changes:

Implemented a clean up function that can be used to
restore a pristine Juju environment, and added a 
test (deploy a charm) demonstrating how to use it.

bin/test-charm now exits with an error if one or 
more tests fail.

Improved browser testing documentation.

QA:

JUJU_GUI_TEST_BROWSERS="chrome firefox ie" \
    bin/test-charm lp:juju-gui

You should see chrome tests passing, all the 
others failing (or raising errors), and the charm 
deployed only once.

https://code.launchpad.net/~frankban/juju-gui/bug-1116698-different-browsers/+merge/148017

(do not edit description out of merge proposal)

[frankban, 2013-02-12 18:11:51]

Please take a look.

[gary.poster, 2013-02-12 18:36:15]

Land as is.  This rocks!  Thanks.  Great docs, helpers and tests.

Gary

[matthew.scott, 2013-02-12 18:56:43]

Land as is.  Thanks for the work!  Good stuff.

[gary.poster, 2013-02-12 19:02:27]

On 2013/02/12 18:36:15, gary.poster wrote:
> Land as is.  This rocks!  Thanks.  Great docs, helpers and tests.
> 
> Gary

For the curious, example output is at http://pastebin.ubuntu.com/1640314/. 
Francesco, please remind me to file bugs for these failures once this branch
lands.  (If you really want to file them yourself, I won't stop you, but I'm
guessing you'd rather me do it :-) )

Gary

[gary.poster, 2013-02-12 23:19:28]

On 2013/02/12 19:02:27, gary.poster wrote:
> On 2013/02/12 18:36:15, gary.poster wrote:
> > Land as is.  This rocks!  Thanks.  Great docs, helpers and tests.
> > 
> > Gary
> 
> For the curious, example output is at http://pastebin.ubuntu.com/1640314/. 
> Francesco, please remind me to file bugs for these failures once this branch
> lands.  (If you really want to file them yourself, I won't stop you, but I'm
> guessing you'd rather me do it :-) )
> 
> Gary

bug 1123562 (firefox) and 
http://sauceio.com/index.php/2012/10/announcing-sauce-support-for-windows-8-a...
:

"We’re still working out some of the kinks, such as making these compatible with
our standard support for self-signed certificates."

For the IE10 issue, then, we may need saucelabs connect per the comment in bug
1117888, plus...something to switch back from https/wss to http/ws?  :-/ not
sure

[frankban, 2013-02-13 09:17:03]

On 2013/02/12 23:19:28, gary.poster wrote:

> bug 1123562 (firefox) and 
>
http://sauceio.com/index.php/2012/10/announcing-sauce-support-for-windows-8-a...

Looking at tests output, we also have at least one unit test failing when run
under Firefox/Selenium. This is new problem, not related to the browser warning.
Added a comment to the bug.

Thanks for the reviews Gary and Matthew!

[frankban, 2013-02-13 09:31:02]

*** Submitted:

Test different browsers using the same env.

Re-deploying the charm to run tests in multiple browsers
is no longer required. Browsers can be specified as space
separated values in the environment variable 
JUJU_GUI_TEST_BROWSERS. Chrome is the default.

Note that currently only chrome tests pass.

Other changes:

Implemented a clean up function that can be used to
restore a pristine Juju environment, and added a 
test (deploy a charm) demonstrating how to use it.

bin/test-charm now exits with an error if one or 
more tests fail.

Improved browser testing documentation.

QA:

JUJU_GUI_TEST_BROWSERS="chrome firefox ie" \
    bin/test-charm lp:juju-gui

You should see chrome tests passing, all the 
others failing (or raising errors), and the charm 
deployed only once.

R=gary.poster, matthew.scott
CC=
https://codereview.appspot.com/7307104