<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Thank you guys for all your help! Special thanks to Robert who helped to find a workaround for an issue [1] that didn’t let us use testr for Fuel Client. The patch [2] was merged and both unit and functional tests are launched by subunit and the data is maintained by testrepository.<div class=""><div class=""><div class=""><br class=""></div><div class="">Please also note that in order to facilitate debugging two additional tox environments — dbgunit or dbgfunc, were introduced for either unit or functional tests.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">1. <a href="https://bugs.launchpad.net/testrepository/+bug/1504310" class="link" rel="noreferrer" target="_blank">https://bugs.launchpad.net/testrepository/+bug/1504310</a></div><div class="">2. <a href="https://review.openstack.org/#/c/227895/" class="">https://review.openstack.org/#/c/227895/</a></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">- romcheg</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">9 жовт. 2015 р. о 01:51 Roman Prykhodchenko <<a href="mailto:me@romcheg.me" class="">me@romcheg.me</a>> написав(ла):</div><br class="Apple-interchange-newline"><div class=""><div class="">Folks,<br class=""><br class="">Since we’ve reached the consensus here I’d like to invite you to review the patch [1] that replaces py.test with testr without making debuging or running specific tests harder. Please also note that it has a dependency which needs to be reviewed and merged first one.<br class=""><br class="">1. <a href="https://review.openstack.org/#/c/227895" class="">https://review.openstack.org/#/c/227895</a><br class=""><br class=""><br class="">- romcheg<br class=""><br class=""><br class=""><blockquote type="cite" class="">7 жовт. 2015 р. о 14:41 Roman Prykhodchenko <<a href="mailto:me@romcheg.me" class="">me@romcheg.me</a>> написав(ла):<br class=""><br class="">Michał,<br class=""><br class="">some comments in-line<br class=""><br class=""><blockquote type="cite" class=""><blockquote type="cite" class="">- testrepository and related components are used in OpenStack Infra<br class="">environment for much more tasks than just running tests<br class=""></blockquote><br class="">If by "more tasks" you mean parallel testing, py.test also has a<br class="">possibility to do that by pytest-xdist.<br class=""></blockquote><br class="">As Monthy mentioned, it’s not only about testing, it’s more about deeper integration with OpenStack Infra.<br class=""><br class=""><br class=""><blockquote type="cite" class=""><blockquote type="cite" class="">- py.test won’t be added to global-requirements so there always be a chance<br class="">of another dependency hell<br class=""></blockquote><br class="">As Igor Kalnitsky said, py.test doesn't have much requirements.<br class=""><a href="https://github.com/pytest-dev/pytest/blob/master/setup.py#L58" class="">https://github.com/pytest-dev/pytest/blob/master/setup.py#L58</a><br class="">It's only argparse, which already is in global requirements without<br class="">any version pinned.<br class=""></blockquote><br class="">It’s not only about py.test, there is an up-to-date objective of sticking all requirements to global-requirements because we have big problems because of that every release.<br class=""><br class=""><blockquote type="cite" class=""><br class="">Cheers,<br class="">Michal<br class=""><br class="">__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></blockquote><br class="">__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></blockquote><br class="">__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></div></blockquote></div><br class=""></div></div></div></body></html>