Bug 1165503

Summary:	[RFE][ceilometer]: Declarative HTTP API Tests
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-ceilometer	Assignee:	Eoghan Glynn <eglynn>
Status:	CLOSED ERRATA	QA Contact:	Yurii Prokulevych <yprokule>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	jruzicka, markmc, pbrady, rrosa, yeylon
Target Milestone:	Upstream M2	Keywords:	FutureFeature, OtherQA, Triaged
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/ceilometer/+spec/declarative-http-tests
Whiteboard:	upstream_milestone_kilo-2 upstream_definition_approved upstream_status_implemented
Fixed In Version:	openstack-ceilometer-2015.1.0-2.el7ost	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:16:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description RHOS Integration 2014-11-19 05:04:48 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/ceilometer/+spec/declarative-http-tests.

Description:

This spec proposes a suite of "grey-box" tests for the Ceilometer HTTP API that are driven by one or several human-readable text files that declare URL requests alongside expected responses. These tests will provide end to end tests of API endpoints that in addition to confirming the functionality of the API will provide a cogent and readable overview of the HTTP API.

Specification URL (additional information):

https://github.com/openstack/ceilometer-specs/blob/master/specs/kilo/declarative-http-tests.rst

Comment 6 Yurii Prokulevych 2015-07-21 08:43:07 UTC

Running test manually:
gabbi-run X.X.X.X:8777 < /usr/lib/python2.7/site-packages/ceilometer/tests/gabbi/gabbits/alarms.yaml                                                      
... ✓ list alarms none: Lists alarms, none yet exist
... o try to PUT an alarm: what does PUT do
        [expected failure]
... o createAlarm: Creates an alarm.
        [expected failure]
... ✓ showAlarm: Shows information for a specified alarm.
... ✓ updateAlarm: Updates a specified alarm.
... ✓ showAlarmHistory: Assembles the history for a specified alarm.
... ✓ updateAlarmState: Sets the state of a specified alarm.
... ✓ list alarms for data: Lists alarms, only one
... ✓ showAlarmState: Gets the state of a specified alarm.
... ✓ list alarms one: Lists alarms, only one
... ✓ deleteAlarm: Deletes a specified alarm.
... ✓ list alarms none end: Lists alarms, none now exist

----------------------------------------------------------------------
Ran 12 tests in 0.659s

OK (expected failures=2)

Comment 8 errata-xmlrpc 2015-08-05 13:16:10 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2015:1548