[openstack-dev] [Fuel] Feature delivery rules and automated tests
mscherbakov at mirantis.com
Tue Dec 23 23:20:14 UTC 2014
would that be possible?
On Mon, Dec 22, 2014 at 7:49 PM, Anastasia Urlapova <aurlapova at mirantis.com>
> Mike, Dmitry, team,
> let me add 5 cents - tests per feature have to run on CI before SCF, it is
> mean that jobs configuration also should be implemented.
> On Wed, Dec 17, 2014 at 7:33 AM, Mike Scherbakov <mscherbakov at mirantis.com
> > wrote:
>> I fully support the idea.
>> Feature Lead has to know, that his feature is under threat if it's not
>> yet covered by system tests (unit/integration tests are not enough!!!), and
>> should proactive work with QA engineers to get tests implemented and
>> passing before SCF.
>> On Fri, Dec 12, 2014 at 5:55 PM, Dmitry Pyzhov <dpyzhov at mirantis.com>
>>> we've done a good job in 6.0. Most of the features were merged before
>>> feature freeze. Our QA were involved in testing even earlier. It was much
>>> better than before.
>>> We had a discussion with Anastasia. There were several bug reports for
>>> features yesterday, far beyond HCF. So we still have a long way to be
>>> perfect. We should add one rule: we need to have automated tests before HCF.
>>> Actually, we should have results of these tests just after FF. It is
>>> quite challengeable because we have a short development cycle. So my
>>> proposal is to require full deployment and run of automated tests for each
>>> feature before soft code freeze. And it needs to be tracked in checklists
>>> and on feature syncups.
>>> Your opinion?
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>> Mike Scherbakov
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev