Skip to content
greese edited this page Mar 13, 2013 · 12 revisions

The goal of the Dasein Cloud Test Suite is to verify that each implementation of Dasein Cloud behaves in the same manner as the others with respect to the capabilities the implementation supports. Because of the variety of API calls it makes, it is one of the more comprehensive systems for testing cloud APIs.In fact, the test suite is just as likely to uncover bugs in the underlying cloud as it is in your implementation code.

Most of the documentation here covers the test suite for Dasein cloud 2013.04 and later. There's a page of documentation on the test suite for version 2013.02 and earlier.

Capabilities

  • Integration testing of expected responses from a cloud API based on the Dasein Cloud interfaces
  • Test coverage for a large portion of the Dasein Cloud API
  • Management and re-use of provisioned resources across multiple tests
  • Safe provisioning/removal of objects to avoid interfering with any existing resources in a cloud account
  • Ability to run individual tests, groups of tests or the full test suite based on need
  • Reporting on API usage, objects provisioned and encountered, and resources de-provisioned
  • Separation of tests into stateless and stateful tests
  • Very good at helping you uncover setup problems in your OpenStack and CloudStack deployments

Contents

A Note on Resource Usage

If you are running these tests against a public cloud, these tests are provisioning resources and costing you money. In some clouds, they may cost you a lot of money. Furthermore, the tests TRY to clean up after themselves, but there is no guarantee they will be successful, especially if you terminate the test run manually. YOU SHOULD ALWAYS MANUALLY VERIFY CLEAN UP AFTER RUNNING THE TESTS. FAILURE TO DO SO WILL RESULT IN YOUR CLOUD PROVIDER CHARGING YOU FOR POINTLESS, UNUSED RESOURCES. If I could make that text blink without offending people, I would.