lp:~frankban/charms/trusty/juju-gui/test-fixes

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:~juju-gui/charms/trusty/juju-gui/trunk at revision 226

Juju GUI Hackers: Pending requested 2015-01-05

Diff: 193 lines (+23/-29)

9 files modified

Makefile (+3/-2)
server-requirements.pip (+3/-3)
server/guiserver/__init__.py (+1/-1)
server/guiserver/clients.py (+0/-16)
server/guiserver/tests/test_clients.py (+1/-1)
server/guiserver/tests/test_handlers.py (+1/-1)
server/guiserver/tests/test_utils.py (+10/-1)
server/guiserver/utils.py (+2/-2)
tests/tests.yaml (+2/-2)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1402061: The juju-gui charm fails automated testing

High

Fix Released

Link a bug report

Related blueprints

229. By Francesco Banconi on 2015-01-05

Add a note to the Makefile about tests/tests.yaml.

228. By Francesco Banconi on 2015-01-05

Lint.

227. By Francesco Banconi on 2015-01-05

Fix httpclient body GET requests with new Tornado. Bump GUI server version up.

226. By Francesco Banconi on 2015-01-05

Update GUI server dependencies and fix tests.

225. By Jeff Pihach on 2014-12-18

Converted showGetJujuButton to hideLoginButton to match UI changes in the GUI

224. By Francesco Banconi on 2014-12-17

Support deploying bundles from custom users.

Also add the charmstore-url charm option so
that the new GUI can properly connect to the
charm store.

Update the deployer version (we use a fork for now)
and the GUI server so that both the user and the
password are provided when calling the deployer
blocking functions.

If you are curious, the deployer merge proposal is here:
https://code.launchpad.net/~frankban/juju-deployer/guiserver-auth/+merge/244984

Tests: `make unittest`.

QA:
- bootstrap an environment with juju 1.21;
- deploy this charm by using `make deploy`;
- wait for the charm to be ready;
- switch to the most recent GUI:
  `juju set juju-gui juju-gui-source=develop`;
- while waiting, create a new juju user:
  `juju user add new-user --generate`;
- copy to clipboard the password included in the
  resulting new-user.jenv file;
- wait for the trunk release to be ready;
- visit the GUI and log in using "new-user" and
  the copied password;
- ensure the charm browser is correctly displayed, meaning
  the charm properly connects to the charm store;
- search for a bundle in the browser and deploy it: you should
  get this error: "An error occurred while deploying the bundle:
  Invalid relation in config, service 1 not found, rel 1 <-> 0
  Invalid relation in config, service 0 not found, rel 1 <-> 0"
  or similar... This is another issue. Dragging and dropping an old
  bundle from your desktop should instead work;
- destroy the environment.

Done, thank you!

R=
CC=
https://codereview.appspot.com/191940043

223. By Francesco Banconi on 2014-12-10

Add the Juju version to the GUI config file.

The version can be specified using a charm option.
If not specified, the Juju version is retrieved
dynamically by calling jujud --version.

Initial implementation by Huw.

Tests: `make unittest`.

QA:
- bootstrap an environment;
- run `make deploy`;
- wait for the unit to be ready;
- run `juju ssh juju-gui/0 cat /var/lib/juju-gui/juju-gui/build-prod/juju-ui/assets/config.js`
  and check the Juju version is included in the config file;
- run `juju set juju-gui juju-core-version=42.47`;
- check the version is changed to the one specified;
- run `juju unset juju-gui juju-core-version`;
- check the correct version is back in the config file;
- destroy the environment.

Done, thank you!

R=rharding
CC=
https://codereview.appspot.com/188890043

222. By Jeff Pihach on 2014-11-27

Merged back the new charm release.

221. By Jeff Pihach on 2014-11-27

Updated to the newest juju-gui release.

220. By Francesco Banconi on 2014-11-18

Merged back the new charm release.