Move success response checking to tempest clients

Registered by David Kranz on 2014-05-09

To ensure API stability, api calls from tempest should check that the response
code in the success case is the expected value. Right now these checks are done
by the callers of the apis and in an inconsistent way. There is no policy or
guideline for when to check. It would be better if the response code was
always checked and api callers did not have to worry about this.

Pad for tracking who is doing each service https://etherpad.openstack.org/p/bp-client-checks-success

This blueprint is not quite complete as nova has not been done. But this blueprint will be superseded by https://blueprints.launchpad.net/tempest/+spec/clients-return-one-value so it
is not worth doing anything more with this one.

Blueprint information

Status:
Complete
Approver:
Matthew Treinish
Priority:
Medium
Drafter:
David Kranz
Direction:
Approved
Assignee:
David Kranz
Definition:
Approved
Series goal:
Accepted for juno
Implementation:
Implemented
Milestone target:
milestone icon juno-3
Started by
Matthew Treinish on 2014-07-03
Completed by
David Kranz on 2014-10-21

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/client-checks-success,n,z

Addressed by: https://review.openstack.org/93037
    Add spec for checking success response in clients

Addressed by: https://review.openstack.org/101310
    Add client response checking for image service

Gerrit topic: https://review.openstack.org/#q,topic:bug/1336826,n,z

Addressed by: https://review.openstack.org/104290
    First part of moving success response checking to identity client

Gerrit topic: https://review.openstack.org/#q,topic:bp/savanna-api-tests,n,z

Addressed by: https://review.openstack.org/108363
    Add client response checking for data processing service

Addressed by: https://review.openstack.org/90306
    Adds the clients and tests for CINDER QoS V1 & V2 APIs

Addressed by: https://review.openstack.org/114186
    Move API response success check to Neutron client

Addressed by: https://review.openstack.org/114783
    Update volume client check success

Addressed by: https://review.openstack.org/115238
    Updated the baremetal client for bp client-checks-success

Gerrit topic: https://review.openstack.org/#q,topic:Test-Port-User-Defined-Mac,n,z

Addressed by: https://review.openstack.org/115671
    Updated database clients for bp client-checks-success

Addressed by: https://review.openstack.org/115871
    Updated telemetry client for bp client-checks-success

Gerrit topic: https://review.openstack.org/#q,topic:Test-Port-No-Security-Group,n,z

Addressed by: https://review.openstack.org/116225
    Client response checking for orchestration service

Addressed by: https://review.openstack.org/116435
    Updated compute keypair clients for bp client-checks-success

Addressed by: https://review.openstack.org/117193
    Add client response checking for object storage service

Addressed by: https://review.openstack.org/117621
    Move success response checking to the token client

Addressed by: https://review.openstack.org/117778
    Move response code checking to client for v3 identity tests

Addressed by: https://review.openstack.org/125570
    Remove Resp status code checks in stress tests

Addressed by: https://review.openstack.org/125895
    Move status check to client for "messaging" tests

Addressed by: https://review.openstack.org/134555
    Make every swift clients use expected_success

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.