[openstack-qa] Refactoring Tempest service clients

Jay Pipes jaypipes at gmail.com
Mon Jul 1 18:18:39 UTC 2013


On 07/01/2013 11:28 AM, Sean Dague wrote:
> The point of things in the api/ directory is to test the API, which is
> why we have those clients, and those tests. It's actually a core
> purpose of the test suite. It's also a core purpose to be explicit
> about return codes, so those have to be exposed to the tests. That's
> part of the thing we are testing, for the API portion of the test
> tree. It's not a side effect, it's actually the whole purpose of the
> tests. It's double entry book keeping for our API, yes its effort, but
> you can't have a stable API unless you do it.
>
> Anyway, we've been around in circles about this a few times now in the
> last 2 months. Specific cleanups are welcomed, and will be reviewed.
> So please be specific and not general in this space. Gutting API
> testing is not welcomed or appropriate.
>
> Scenario/ is designed for tests that you want to use the official
> clients. It's totally ok to add more complicated tests over there
> which aren't API tests.
>
> Lastly, I'm actually out on vacation for the week, so expect
> substantial, if not complete ignoring of threads here until I get
> back.

This is exactly how I feel as well.

-jay




More information about the openstack-qa mailing list