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 <dpyz...@mirantis.com> wrote: > > Guys, > > 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@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Mike Scherbakov #mihgen
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev