Hi,
On Thu, Mar 26, 2015 at 10:26 PM, Zane Bitter zbit...@redhat.com wrote:
On 26/03/15 10:38, Pavlo Shchelokovskyy wrote:
Hi all,
following IRC discussion here is a summary of what I propose can be done
in this regard, in the order of increased decoupling:
1) make a separate
Hello,
As a QA engineer, I like the idea to make integration tests more
independent and have an ability to package them and run against any
deployed cloud, it will be very useful.
But I assume, that creating a separate repository is not needed and it is
enough to just collect all
On 03/27/2015 06:57 AM, Pavlo Shchelokovskyy wrote:
Hi,
On Thu, Mar 26, 2015 at 10:26 PM, Zane Bitter zbit...@redhat.com
mailto:zbit...@redhat.com wrote:
[snip]
3) move the integration tests to a separate repo and use it as git
submodule in the main tree. The main
On Fri, Mar 27, 2015 at 6:26 AM, Zane Bitter zbit...@redhat.com wrote:
On 26/03/15 10:38, Pavlo Shchelokovskyy wrote:
Hi all,
following IRC discussion here is a summary of what I propose can be done
in this regard, in the order of increased decoupling:
1) make a separate requirements.txt
On 03/26/2015 10:38 AM, Pavlo Shchelokovskyy wrote:
Hi all,
following IRC discussion here is a summary of what I propose can be
done in this regard, in the order of increased decoupling:
1) make a separate requirements.txt for integration tests and modify
the tox job to use it. The code
On 26/03/15 10:38, Pavlo Shchelokovskyy wrote:
Hi all,
following IRC discussion here is a summary of what I propose can be done
in this regard, in the order of increased decoupling:
1) make a separate requirements.txt for integration tests and modify the
tox job to use it. The code of these
