Testing Fixtures

How do I create fixtures to use in a Mimic test?

When using Mimic, it’s best to create resources as you would with a real cloud: write a script in your testing tool to provision the resources you depend on, authenticate, and issue real public API requests to create them. For example, if you need some servers to connect to a load balancer, just authenticate and use the Nova API to create servers in the appropriate region where you’re going to be doing your load balancer testing.

However, we (the Mimic team) are keenly aware that test resource set-up can be tedious, and we want to mitigate that as much as possible. What we don’t want to do is create weird ways to create your test resources which are 90% as much work as the real public API requests that you would have to make, but that are special and specific to mimic.

We’re interested to hear what your test set-up is like and if mimic can add any features to make it easier. One thing that we have discussed potentially doing is to have a way to configure mimic to do more or less validation by default; for example, we intend to eventually implement validation of the auth token and glance image specification in Nova (neither of which are currently done), but preserve the ability to turn those off to save work for tests that are testing some specific error condition and wouldn’t be able to run against a real cloud unmodified anyway because a real cloud couldn’t provoke that error.