Some notes on what's missing or out of date in the existing gabbi test for ceilometer and gnocchi.
Gnocchi
Existing
- gabbits-list/live.yaml could be made more readable with json paths
- archive.yaml multiple xfail
- base.yaml bad formatting and lack of comments
- metric.yaml lack of comments
- resource.yaml xfail at /v1 (lack of content)
Coverage
Enough here that probably best to just drive by way of the coverage data: tox -epy27-cover -- gabbi
- send non-uuid x-user-id and x-project-id
- ValidAggeMethod (provide a bad aggregation, see what happens)
- try to create an archive policy rule that already exists
- get one archive policy rule
- get one non-existent archive policy rule
- attempt to delete an archive policy rule that is currently in use (what does in use mean here)
- Aggregations, across the board
- Post measures on metric that does not exist
- Post measures on metric that are too old
- Getting measures in a variety of ways
- ETag handling
- NamedMetric handling
- Searches
Ceilo
Existing
- alarms.yaml using older formatting and lack of comments
- api_events*.yaml not indented
- basic.yaml demonstrates a bug with an xfail or reported bug
- meters.yaml has wsme related xfails
- meters.yaml has 'faulstring' typo on an xfailing test
Coverage
- RBAC enforcement
- ParsableErrorMiddleware (WAT?)
- Query sanitation (from v2.utils, will require a model of projects and users)
- ValidatedComplexQuery (v2.query)
- event query to event filter (v2.events)
- error handling in Query (v2.base)
- misc aspects of alarms
- gnocchi drive alarms
- alarm combination rules