On Thu, 22 Jun 2017, Shewale, Bhagyashri wrote:
* who or what needs to consume these JSON samples?The users of placement API can rely on the request/response for different supported placement versions based on some tests running on the OpenStack CI infrastructure. Right now, most of the placement APIs are well documented and others are in progress but there are no tests to verify these APIs.
Either we are misunderstanding each other, or you're not aware of what the gabbi tests are doing. They verify the placement API and provide extensive coverage of the entire placement HTTP framework, including the accuracy of response codes in edge cases not on the "happy path". Coverage is well over 90% for the group of files in nova/api/openstack/placement (except for the wsgi deployment script itself) when the nova/tests/functional/api/openstack/placement/test_placement_api.py functionl tests runs all the gabbi files in nova/tests/functional/api/openstack/placement/gabbits/. So I'd say the api is verified. What is missing, and could be useful, is using those tests to get accurate and up to date representations of the JSON request and response bodies. If that's something we'd like to pursue as I said in my other message the 'verbose' functionality that can be provided in gabbi-based tests should be able to help.
We would like to write new functional test to consume these json samples to verify each placement API for all supported versions.
Those gabbi files also test functionality at micorversion boundaries. -- Chris Dent ┬──┬◡ノ(° -°ノ) https://anticdent.org/ freenode: cdent tw: @anticdent
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev