<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 31/08/16 19:59, Alan Pevec wrote:<br>
</div>
<blockquote
cite="mid:CABYd8SePKQtWOy1BWVhuZWoM1x+F+LBkhzydDeKjeEDiXAZ3Xg@mail.gmail.com"
type="cite">
<pre wrap="">On Tue, Aug 30, 2016 at 11:45 PM, Steve Baker <a class="moz-txt-link-rfc2396E" href="mailto:sbaker@redhat.com"><sbaker@redhat.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">We've discussed this multiple times and each time the consensus has been to
leave the tests in-tree. Developers really like the convenience in including
a functional/integration test in the same commit as a bug or feature. This
means there are currently no plans to create a new repo for heat tempest
tests.
</pre>
</blockquote>
<pre wrap="">
But how will you handle in-tree Tempest plugin in stable branches?
Tempest is branchless and other in-tree plugins have been doing ugly
things like checking out specific Tempest commit which is not
packageable :(
Alan
</pre>
</blockquote>
<p><font face="Hack">We're doing the following, which I think will
mitigate branchless concerns for now:</font></p>
<p><font face="Hack">- minimal dependency on tempest imports, only
tempest.config and tempest.test_discover.plugins</font></p>
<p><font face="Hack">- self contained config in the [heat_plugin]
namespace</font></p>
<p><font face="Hack">- config options like skip_functional_test_list
and skip_scenario_test_list so that latest tests can run against
an old API which lacks the required features for all tests</font></p>
<p><font face="Hack"><br>
I realize keeping tests in-tree is a hassle for downstream
packaging, at least for now I'm in favor of keeping them in-tree
but I will raise packaging concerns when we discuss this again.</font></p>
<p><font face="Hack"><br>
cheers</font></p>
</body>
</html>