Make tests more reliable

Make tests more reliable

- When an app is instantiated, always make the connection a no-op if possible to prevent unnecessary additional postponed calls.
- When an app is instantiated, always set the view to a no-op view to prevent routing.

Those two fixes prevent intermittent errors that have been showing up on CI and killing our runs when Canonistack isn't doing that for us.

- Change the compressed file to be called modules.js.  This contains all of the modules, rather than pointing to them, as it does in devel/debug.  This makes our tests pass in individual suites now.

https://code.launchpad.net/~gary/juju-gui/testclean/+merge/157941

(do not edit description out of merge proposal)

[gary.poster, 2013-04-09 19:29:56]

Please take a look.

[matthew.scott, 2013-04-09 19:44:56]

LGTM - should be much cleaner, thanks!

https://codereview.appspot.com/8580046/diff/1/Makefile
File Makefile (right):

https://codereview.appspot.com/8580046/diff/1/Makefile#newcode157
Makefile:157: @echo "test-prod-server: run tests in the browser from the prod
environment"
Very big +1 :)

[gary.poster, 2013-04-09 19:58:39]

*** Submitted:

Make tests more reliable

- When an app is instantiated, always make the connection a no-op if possible to
prevent unnecessary additional postponed calls.
- When an app is instantiated, always set the view to a no-op view to prevent
routing.

Those two fixes prevent intermittent errors that have been showing up on CI and
killing our runs when Canonistack isn't doing that for us.

- Change the compressed file to be called modules.js.  This contains all of the
modules, rather than pointing to them, as it does in devel/debug.  This makes
our tests pass in individual suites now.

R=matthew.scott
CC=
https://codereview.appspot.com/8580046