Waiting for this review on wsme to get through. Turned out to be considerably more of a slog than initially expected. Content-Negotiation was completely broken in the WSME.

It also appears to have a problem with properly dealing with 405 responses when the wrong method is sent to an endpoint.

Slope

• watch the review and see when/how to integrate in the gabbi tests for ceilo
• otherwise carry on with gabbi

Review

Discussion with dkranz in os-qa about API tests in tempest led to pointing out the two etherpads related to the scope of the tempest and moving tests to in-tree. It is likely that gabbi can have a role here on those tests which do not require either of:

• another project to validate the results
• python code to validate the results

The latter is not fungible, but the first is: We could spin up devstack or dox envs to handle other projects if necessary.

Given the new tent governance policies, the need to test better and the fact that every time I go to test something I find a huge bug somewhere (see above) it would easily be possible to work on just test improvement for the rest of time. I'd be pretty okay with that.