Re: [openstack-dev] [Fuel][library] Switching to external fixtures for integration Noop tests

An update. The task is done, the noop tests framework now has automatic docs builds to readthedocs [0] and a Fuel infra CI gate that tests changes against the fuel-library master, by running existing integration noop rspecs. So the CI is now mutual: changes to the fuel library are tested against

Re: [openstack-dev] [Fuel][library] Switching to external fixtures for integration Noop tests

Hello, an update inline! On 27.01.2016 17:37, Bogdan Dobrelya wrote: > On 26.01.2016 22:18, Kyrylo Galanov wrote: >> Hello Bogdan, >> >> I hope I am not the one of the context. Why do we separate fixtures for >> Noop tests from the repo? >> I can understand if while noop test block was carried

Re: [openstack-dev] [Fuel][library] Switching to external fixtures for integration Noop tests

On 26.01.2016 22:18, Kyrylo Galanov wrote: > Hello Bogdan, > > I hope I am not the one of the context. Why do we separate fixtures for > Noop tests from the repo? > I can understand if while noop test block was carried out to a separate > repo. > I believe fixtures normally are downloaded by

Re: [openstack-dev] [Fuel][library] Switching to external fixtures for integration Noop tests

Hello Bogdan, I hope I am not the one of the context. Why do we separate fixtures for Noop tests from the repo? I can understand if while noop test block was carried out to a separate repo . On Tue, Jan 26, 2016 at 1:54 PM, Bogdan Dobrelya wrote: > We are going to

[openstack-dev] [Fuel][library] Switching to external fixtures for integration Noop tests

We are going to switch [0] to external astute.yaml fixtures for Noop tests and remove them from the fuel-library repo as well. Please make sure all new changes to astute.yaml fixtures will be submitted now to the new location. Related mail thread [1]. [0]