On 30/08/16 19:55, Alan Pevec wrote:
> The solution is a little unconventional though so it will need
some
> feedback. What it does is to do a standard python install then
> duplicate the egg-info directory and manipulate it to resemble a dedicated
> tempest plugin package.
>
> 
https://review.rdoproject.org/r/#/c/1980/
 I like that as a workaround for in-tree tempest plugins but proper
 solution is really that upstream project creates a separate repo for
 their tempest plugin. Is that in progress for Heat?
 
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.