Stress test framework should track and report api success/failures
When a stress test calls an api, say volume_
that api call and note that it was successfull or failed. When the stress test is done, it should have the option
of dumping out the api calls and their success/fail rate.
Something like this (as a cinder test example)
[2013-05-
[2013-05-
[2013-05-
[2013-05-
[2013-05-
[2013-05-
[2013-05-
[2013-05-
[2013-05-
[2013-05-
[2013-05-
[2013-05-
[2013-05-
[2013-05-
[2013-05-
[2013-05-
Blueprint information
- Status:
- Complete
- Approver:
- Matthew Treinish
- Priority:
- Medium
- Drafter:
- Walt Boring
- Direction:
- Approved
- Assignee:
- Ramy Asselin
- Definition:
- Obsolete
- Series goal:
- Accepted for juno
- Implementation:
- Unknown
- Milestone target:
- juno-3
- Started by
- Completed by
- Ramy Asselin
Related branches
Related bugs
Sprints
Whiteboard
3/13/2014: Sample output of a 3.5 hour cinder CHO test: http://
Gerrit topic: https:/
Addressed by: https:/
Track API call success & failures in stress tests
Gerrit topic: https:/
Addressed by: https:/
Add qa spec for bp:stress-
Work Items
Work items:
[walter-boring] API Statistics Wrapper: DONE
[ramy-asselin] Stabilize API Statistics Wrapper: DONE
[walter-boring] Cinder Stress Test: DONE
[ramy-asselin] Stabilize Cinder Stress Tests: INPROGRESS
[ramy-asselin] Cinder CHO Test: DONE
[ramy-asselin] Cinder CHO Stabilize: INPROGRESS
[ramy-asselin] Extend Cinder tests: TODO
[ramy-asselin] Code Cleanup: TODO