launchpad-reviewers team mailing list archive

[Diogo Matsubara <matsubara@xxxxxxxxxxxxx>]

Diogo Matsubara has proposed merging lp:~matsubara/maas/checkbox-acceptance-tests into lp:maas.

Requested reviews:
  Launchpad code reviewers (launchpad-reviewers)

For more details, see:
https://code.launchpad.net/~matsubara/maas/checkbox-acceptance-tests/+merge/96825

This branch adds the initial checkbox acceptance tests for MaaS broken down from user stories.

I added a new make target (make checkbox) to run those test and instructions in the HACKING.txt document on how to run and install checkbox.

Please advise where in the tree is appropriate place for these tests to live.

Cheers,

Diogo
-- 
https://code.launchpad.net/~matsubara/maas/checkbox-acceptance-tests/+merge/96825
Your team Launchpad code reviewers is requested to review the proposed merge of lp:~matsubara/maas/checkbox-acceptance-tests into lp:maas.

=== modified file 'HACKING.txt'
--- HACKING.txt	2012-03-09 14:50:53 +0000
+++ HACKING.txt	2012-03-09 20:16:23 +0000
@@ -209,3 +209,20 @@
 
 .. _convention for headings as used in the Python documentation:
   http://sphinx.pocoo.org/rest.html#sections
+
+Acceptance tests
+================
+
+MaaS uses checkbox manual testing infrastructure to verify features are implemented according to the spec. They can be found in the checkbox-tests directory.
+
+You need to install checkbox to use those tests.
+
+    $ sudo apt-get install checkbox
+
+To run them:
+
+    $ checkbox-gtk --config=--config='checkbox/plugins/jobs_info/directories=/path/to/local/checkbox/jobs/dir' --whitelist-file=
+
+or run from the root of the MaaS tree:
+
+    $ make checkbox

=== modified file 'Makefile'
--- Makefile	2012-02-15 17:13:37 +0000
+++ Makefile	2012-03-09 20:16:23 +0000
@@ -93,6 +93,9 @@
 syncdb: bin/maas dev-db
 	bin/maas syncdb --noinput
 
+checkbox:
+	checkbox-gtk --config='checkbox/plugins/jobs_info/directories=$(PWD)/checkbox-tests/' --whitelist-file=
+
 .PHONY: \
     build check clean dev-db distclean doc \
     harness lint pserv-start pserv-stop run \

=== added directory 'checkbox-tests'
=== added file 'checkbox-tests/installer.txt'
--- checkbox-tests/installer.txt	1970-01-01 00:00:00 +0000
+++ checkbox-tests/installer.txt	2012-03-09 20:16:23 +0000
@@ -0,0 +1,22 @@
+plugin: manual
+name: installer/enlist
+description:
+ PURPOSE:
+     This test will test that the Ubuntu installer has the option to enlist a node from the boot CD.
+ STEPS:
+     1. Boot Ubuntu from the CD
+     2. Find the option to enlist the machine to a cloud
+ VERIFICATION:
+     Did the installer offered an option to enlist the machine to a cloud?
+
+plugin: manual
+name: installer/server
+description:
+ PURPOSE:
+     This test will test that the Ubuntu installer has the option to install the MaaS server from the CD.
+ STEPS:
+     1. Boot Ubuntu from the CD
+     2. Find the option to install a new MaaS server.
+ VERIFICATION:
+     Did the installer offered an option to install a MaaS server?
+

=== added file 'checkbox-tests/juju.txt'
--- checkbox-tests/juju.txt	1970-01-01 00:00:00 +0000
+++ checkbox-tests/juju.txt	2012-03-09 20:16:23 +0000
@@ -0,0 +1,22 @@
+plugin: manual
+name: juju/bootstrap
+description:
+ PURPOSE:
+     This test will test that you can bootstrap a Juju environment using a MaaS server.
+ STEPS:
+     1. Bootstrap a new environment using juju pointing to a MaaS server.
+     2. Run juju status
+ VERIFICATION:
+     Can you use juju status and see the available nodes?
+
+plugin: manual
+name: juju/deploy
+description:
+ PURPOSE:
+     This test will test that you can succesfully deploy to MaaS nodes using Juju
+ STEPS:
+     1. Bootstrap a new environment using juju pointing to a MaaS server.
+     2. Run juju deploy $someservice
+ VERIFICATION:
+     Can you use juju deploy $someservice and have it deployed in the MaaS
+     node?

=== added file 'checkbox-tests/maas.txt'
--- checkbox-tests/maas.txt	1970-01-01 00:00:00 +0000
+++ checkbox-tests/maas.txt	2012-03-09 20:16:23 +0000
@@ -0,0 +1,27 @@
+plugin: manual
+name: maas/update-images
+description:
+ PURPOSE:
+     This test will test that the MaaS server offers an option to periodically update cloud images.
+ STEPS:
+     1. Open the main page to the MaaS server
+     2. Find the option in the MaaS server preferences to periodically update cloud images.
+     3. Set it to automatically update
+ VERIFICATION:
+     Did you find the option to periodically update cloud images?
+     Were the cloud images updated according to the schedule?
+
+plugin: manual
+name: maas/cache-archives-locally
+description:
+ PURPOSE:
+     This test will test that the MaaS server offers an option to cache archives locally.
+ STEPS:
+     1. Open the main page to the MaaS server
+     2. Find the option in the MaaS server preferences to cache archives
+     locally
+     3. Enable the option
+ VERIFICATION:
+     Did you find the option to cache archives locally?
+     Verify archives are cached locally and nodes are using it to receive updates.
+