[openstack-dev] Thoughts on the patch test failure rate and moving forward

Jay Pipes jaypipes at gmail.com
Sun Jul 27 02:02:18 UTC 2014


On 07/24/2014 06:36 PM, John Dickinson wrote:
> On Jul 24, 2014, at 3:25 PM, Sean Dague <sean at dague.net> wrote:
>> On 07/24/2014 06:15 PM, Angus Salkeld wrote:
>>> We do this in Solum and I really like it. It's nice for the same
>>> reviewers to see the functional tests and the code the implements
>>> a feature.
>>>
>>> One downside is we have had failures due to tempest reworking
>>> their client code. This hasn't happened for a while, but it would
>>> be good for tempest to recognize that people are using tempest as
>>> a library and will maintain API.
>>
>> To be clear, the functional tests will not be Tempest tests. This
>> is a different class of testing, it's really another tox target
>> that needs a devstack to run. A really good initial transition
>> would be things like the CLI testing.
>
> I too love this idea. In addition to the current Tempest tests that
> are run against every patch, Swift has in-tree unit, functional[1],
> and probe[2] tests. This makes it quite easy to test locally before
> submitting patches and makes keeping test coverage high much easier
> too. I'm really happy to hear that this will be the future direction
> of testing in OpenStack.

And Glance has had functional tests in-tree for 3 years:

http://git.openstack.org/cgit/openstack/glance/tree/glance/tests/functional

-jay



More information about the OpenStack-dev mailing list