Merge lp:~mbruzek/charms/precise/couchdb/tests into lp:charms/couchdb

[Matt Bruzek]

Adding tests for this charm

[Cory Johns (johnsca)]

The tests fail for me due to the install hook failing because the path for the open-ports command is wrong.

I submitted a MP against this branch that fixes it and with that change, the tests pass for me: https://code.launchpad.net/~johnsca/charms/precise/couchdb/fix-install/+merge/243549

[Review Queue (review-queue)]

This items has failed automated testing! Results available here http://reports.vapour.ws/charm-tests/charm-bundle-test-10642-results

review: Needs Fixing (automated testing)

[lp:~mbruzek/charms/precise/couchdb/tests]

14. By Matt Bruzek on 2014-12-12

Removing old path to open-port

[José Antonio Rey (jose)]

Even though the open-port error is removed, there is another error for which a bug will be filed. The tests are good, +1.

review: Approve

=== modified file 'hooks/install'
--- hooks/install	2012-02-09 22:51:46 +0000
+++ hooks/install	2014-12-12 16:45:24 +0000
@@ -4,7 +4,7 @@
 
 
 apt-get -y install python-software-properties debconf debconf-utils
-apt-add-repository ppa:facter-plugins/ppa
+apt-add-repository -y ppa:facter-plugins/ppa
 apt-get -y update
 apt-get install -y couchdb facter facter-customfacts-plugin uuid python-couchdb pwgen
 
@@ -28,4 +28,4 @@
 
 service couchdb status && service couchdb restart || service couchdb start
 
-[ -x /usr/bin/open-port ] && open-port `facter couchdb_port`/TCP
+open-port `facter couchdb_port`/TCP
 
=== added directory 'tests'
=== added file 'tests/00-setup'
--- tests/00-setup	1970-01-01 00:00:00 +0000
+++ tests/00-setup	2014-12-12 16:45:24 +0000
@@ -0,0 +1,5 @@
+#!/bin/bash
+
+sudo add-apt-repository ppa:juju/stable -y
+sudo apt-get update
+sudo apt-get install amulet python3-requests -y
 
=== added file 'tests/99-autogen'
--- tests/99-autogen	1970-01-01 00:00:00 +0000
+++ tests/99-autogen	2014-12-12 16:45:24 +0000
@@ -0,0 +1,49 @@
+#!/usr/bin/env python3
+
+import amulet
+import requests
+import unittest
+
+
+class TestDeployment(unittest.TestCase):
+    @classmethod
+    def setUpClass(cls):
+        cls.deployment = amulet.Deployment(series='precise')
+
+        cls.deployment.add('couchdb')
+
+        try:
+            cls.deployment.setup(timeout=900)
+            cls.deployment.sentry.wait()
+        except amulet.helpers.TimeoutError:
+            amulet.raise_status(amulet.SKIP, msg="Environment wasn't stood up in time")
+        except:
+            raise
+
+    def test_case(self):
+        # Now you can use self.deployment.sentry.unit[UNIT] to address each of
+        # the units and perform more in-depth steps.  You can also reference
+        # the first unit as self.unit.
+        # There are three test statuses that can be triggered with
+        # amulet.raise_status():
+        #   - amulet.PASS
+        #   - amulet.FAIL
+        #   - amulet.SKIP
+        # Each unit has the following methods:
+        #   - .info - An array of the information of that unit from Juju
+        #   - .file(PATH) - Get the details of a file on that unit
+        #   - .file_contents(PATH) - Get plain text output of PATH file from that unit
+        #   - .directory(PATH) - Get details of directory
+        #   - .directory_contents(PATH) - List files and folders in PATH on that unit
+        #   - .relation(relation, service:rel) - Get relation data from return service
+        #          add tests here to confirm service is up and working properly
+        # For example, to confirm that it has a functioning HTTP server:
+        #     page = requests.get('http://{}'.format(self.unit.info['public-address']))
+        #     page.raise_for_status()
+        # More information on writing Amulet tests can be found at:
+        #     https://juju.ubuntu.com/docs/tools-amulet.html
+        pass
+
+
+if __name__ == '__main__':
+    unittest.main()