<snip> Also curious about this. It seems weird to separate the 'positive' and the 'negative' ones, assuming those patches are mostly contributed by the same group of developers. </snip>
Yeah, agree. This approach leads to situation when I need to look at two places to observe test coverage for each component. Also when I would like to add some tests I need to contribute to two places which is not convenient for reviewers for contributors IMO. Best regards, Kairat Kushaev On Thu, Mar 17, 2016 at 8:31 AM, Qiming Teng <teng...@linux.vnet.ibm.com> wrote: > > > > I'd love to see this idea explored further. What happens if Tempest > > ends up without tests, as a library for shared code as well as a > > centralized place to run tests from via plugins? > > > > Also curious about this. It seems weird to separate the 'positive' and > the 'negative' ones, assuming those patches are mostly contributed by > the same group of developers. > > Qiming > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
