https://github.com/garethr/digitalocean-expect
Experiments in testing an IaaS
https://github.com/garethr/digitalocean-expect
Last synced: 28 days ago
JSON representation
Experiments in testing an IaaS
- Host: GitHub
- URL: https://github.com/garethr/digitalocean-expect
- Owner: garethr
- License: epl-1.0
- Created: 2014-08-14T14:01:48.000Z (almost 11 years ago)
- Default Branch: master
- Last Pushed: 2015-09-09T11:54:23.000Z (over 9 years ago)
- Last Synced: 2025-03-08T03:48:39.015Z (3 months ago)
- Language: Clojure
- Size: 184 KB
- Stars: 7
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
## What
A very much _work in progress_ example of writing a test suite against
an Infrastructure as a Service, in this case
[DigitalOcean](https://www.digitalocean.com/?refcode=69ef0beac642).
## Why
TDD, ie. using tests to help describe and design your code, is a
well-practices approach to software development. If we really are
treating out _infrastructure as code_ then how about a test suite
picking on certain aspects of a provisioned infrastructure as a service?
This example completely separates the actual testing from the creation
of virtual resources. This isn't a declarative provisioning tool. The
utility I see with that approach is that you could write a simple test
suite and then anyone can create an environment to pass those tests.
This makes certain aspects of portability easier, as well as greatly
simplying the testing half.
## How
The tests are just clojure, although you could implement the same idea
in any language with a suitable IaaS client. The syntax uses
[expectations](http://jayfields.com/expectations/) which leads to some
pretty expressive code:
```clojure
(expect 2 (count nodes))
```
The current [full test
suite](https://github.com/garethr/digitalocean-expect/blob/master/test/clojure/digitalocean_expect/test.clj)
is available in the repository.
## Running
In order to run the tests yourself you'll need a DigitalOcean account.
The underlying client uses the V2 API so you need to set a
`DIGITALOCEAN-ACCESS-TOKEN` environment variables. Alternatively you can use
`.lein-env` if you know what you're doing.
You can run the tests with the following. Note that the specific tests
here are unlikely to pass with anything but the small test dataset I
was using.
lein expectations
Much more fun is running the tests everytime you make a change to the
test file.
lein autoexpect
## Thanks
Thanks to the [digitalocean](https://github.com/owainlewis/digital-ocean)
Clojure client for dealing with the DigitalOcean interface so I could get
on with the job at hand.