<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.6.6">
</HEAD>
<BODY>
Stehen<BR>
<BR>
Yes. These will be additional to functional/unit and exist outside tempest (due to the low-level nature of the tests). Unlike third-party CI, the plan is to keep all efforts upstream since the tests would focus completely on open technology. So we are open to where the tests need to reside. This could be in-tree like a directory called "integration" (along side of "unit" and "functional") here - <A HREF="https://github.com/openstack/nova/tree/master/nova/tests.">https://github.com/openstack/nova/tree/master/nova/tests.</A> <BR>
<BR>
Thanks<BR>
Prasanth<BR>
<BR>
On Mon, 2016-09-26 at 13:08 +0100, Stephen Finucane wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
On Fri, 2016-09-23 at 13:33 -0400, Prasanth Anbalagan wrote:
<FONT COLOR="#737373">> Adding the project to email subject.</FONT>
<FONT COLOR="#737373">> </FONT>
<FONT COLOR="#737373">> Thanks</FONT>
<FONT COLOR="#737373">> Prasanth Anbalagan</FONT>
<FONT COLOR="#737373">> </FONT>
<FONT COLOR="#737373">> On Fri, 2016-09-23 at 12:56 -0400, Prasanth Anbalagan wrote:</FONT>
<FONT COLOR="#737373">> > </FONT>
<FONT COLOR="#737373">> > Hi,</FONT>
<FONT COLOR="#737373">> > </FONT>
<FONT COLOR="#737373">> > Continuing the topic on the need for integration style tests for</FONT>
<FONT COLOR="#737373">> > Nova</FONT>
<FONT COLOR="#737373">> > (brought up earlier during the weekly meeting at #openstack-</FONT>
<FONT COLOR="#737373">> > meeting,</FONT>
<FONT COLOR="#737373">> > Sep 22). The proposal is for a project to hold integration tests</FONT>
<FONT COLOR="#737373">> > that</FONT>
<FONT COLOR="#737373">> > includes low-level testing and runs against a devstack backend. I</FONT>
<FONT COLOR="#737373">> > have</FONT>
<FONT COLOR="#737373">> > included more details here -</FONT>
<FONT COLOR="#737373">> > <A HREF="https://etherpad.openstack.org/p/integration-tests">https://etherpad.openstack.org/p/integration-tests</A></FONT>
<FONT COLOR="#737373">> > </FONT>
<FONT COLOR="#737373">> > Please comment on the need for the project, whether or not any</FONT>
<FONT COLOR="#737373">> > similar</FONT>
<FONT COLOR="#737373">> > efforts are in place, approaches suggested, taking forward the</FONT>
<FONT COLOR="#737373">> > initiative, etc.</FONT>
I missed that conversation, so to clarify, these would be additional
integration tests (as opposed to functional, unit tests) but kept
outside of tempest, correct? If so, how do these differ from what
third-party CIs already provide? [1] If they do provide something
different (i.e. they're run upstream), could these be kept in-tree
(like neutron's scenario tests [2]) rather than in a different project?
Stephen
[1] <A HREF="http://docs.openstack.org/developer/nova/test_strategy.html#infra-v">http://docs.openstack.org/developer/nova/test_strategy.html#infra-v</A>s-third-party
[2] <A HREF="https://github.com/openstack/neutron/blob/master/TESTING.rst#scenar">https://github.com/openstack/neutron/blob/master/TESTING.rst#scenar</A>io-tests
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <A HREF="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</A>?subject:unsubscribe
<A HREF="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</A>
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>