Difference between revisions of "Poppy/Provider - Getting Started/Poppy API Tests"
Amit Gandhi (talk | contribs) |
Amit Gandhi (talk | contribs) |
||
| Line 13: | Line 13: | ||
| − | Once you have docker installed (or boot2docker if using MacOSX or Windows), run the following command: | + | Once you have docker installed (or boot2docker if using MacOSX or Windows), run the following command from your /poppy folder: |
| − | tox -e apidocker api | + | $ tox -e apidocker api |
Revision as of 22:25, 26 January 2015
Running API Tests
API tests for Poppy are run using Tox - [[1]]
We highly recommend running the api tests using Docker, as the docker file will provision a Cassandra storage backend, while keeping your system clean.
There is some initial setup involved.
- Create a fig_local.yaml file.
- Update fig_local.yam with the appropriate configuration values for your provider driver.
- Your local volume of Poppy will be mounted into your container. Make sure your local ~/.poppy/poppy.conf file is updated with your provider references.
- Update your local ~/.poppy/tests.conf file to reference your provider for any flavors created/used by the tests.
Once you have docker installed (or boot2docker if using MacOSX or Windows), run the following command from your /poppy folder:
$ tox -e apidocker api
This will run the api tests against your docker instance.
If all tests are passing, it means the Poppy API has been able to successfully communicate with your API.
