Dmitry I apologize - I did not notice that the commit depends on other ones to Fuel Library which actually improve unit tests coverage. Disregard my previous message, please.
On Fri, Oct 23, 2015 at 2:14 PM, Vladimir Kuklin <[email protected]> wrote: > Dmitry > > These are awesome news. > > BTW, why should we enable unit tests for Fuel Library in voting mode right > now? It seems not all our modules have them passing. Can we wait a bit and > recheck it or we will get our master merges blocked? > > On Fri, Oct 23, 2015 at 3:25 AM, Dmitry Borodaenko < > [email protected]> wrote: > >> Back in July, I proposed a plan to implement PTI in Fuel [0] during Fuel >> 8.0 development cycle, with the following mandatory stages: >> >> Stage 1: Create non-voting gate jobs for a single Fuel repo. >> Stage 2: Get these gate jobs to pass and make them voting. >> Stage 3: Create non-voting gate jobs for all Fuel repos. >> Stage 4: Cover all Fuel repos with voting unit test gate jobs. >> >> and bonus stages: >> >> Stage 5: Add functional tests for Fuel UI and Fuel Library to the gates. >> Stage 6: Run fuel-qa (multi-node deployment) tests on OpenStack Infra. >> >> [0] >> http://lists.openstack.org/pipermail/openstack-dev/2015-July/069908.html >> >> With the Kilo based Fuel 7.0 released in September, we were finally able >> to make some solid progress on that. Of 21 non-plugin Fuel repositories >> on review.openstack.org, 12 (including one of our two largest core >> components: fuel-web) already have voting gate jobs, 3 more (including >> the other largest core component: fuel-library) have passing gate jobs >> that can become voting once all outstanding fixes are merged, and 3 more >> are a work in progress. >> >> Voting: >> - fuel-agent >> - fuel-dev-tools >> - fuel-devops >> - fuel-mirror >> - fuel-octane >> - fuel-ostf (pep8; python gates are waiting for images with gevent) >> - fuel-plugins >> - fuel-specs >> - fuel-stats >> - fuel-upgrade >> - fuel-web >> - python-fuelclient >> >> Ready to vote: >> - fuel-library (needs https://review.openstack.org/238628) >> - fuel-menu >> - shotgun >> >> Work in progress: >> - fuel-astute (has unit tests, needs a gate job) >> - fuel-docs (docs gate job is failing) >> - network-checker (unit test gate job is failing) >> >> Not covered by unit tests: >> - fuel-main (scripts to make Fuel ISO) >> - fuel-nailgun-agent (588 lines of Ruby) >> - fuel-qa (Fuel deployment system tests) >> >> While it might be a bit too early to pull out a "Mission Accomplished" >> banner, it's safe to say that vast majority of Fuel code is now covered >> by gate checks running unit tests and syntax checks on OpenStack CI. >> >> Nice work Alexey, Alex, Alexander, Sebastian, Vladimir, and Vladimir! >> Many thanks to the OpenStack Infra team for encouraging and supporting >> this effort! >> >> -- >> Dmitry Borodaenko >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> [email protected]?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > > -- > Yours Faithfully, > Vladimir Kuklin, > Fuel Library Tech Lead, > Mirantis, Inc. > +7 (495) 640-49-04 > +7 (926) 702-39-68 > Skype kuklinvv > 35bk3, Vorontsovskaya Str. > Moscow, Russia, > www.mirantis.com <http://www.mirantis.ru/> > www.mirantis.ru > [email protected] > -- Yours Faithfully, Vladimir Kuklin, Fuel Library Tech Lead, Mirantis, Inc. +7 (495) 640-49-04 +7 (926) 702-39-68 Skype kuklinvv 35bk3, Vorontsovskaya Str. Moscow, Russia, www.mirantis.com <http://www.mirantis.ru/> www.mirantis.ru [email protected]
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
