+1! I’ve been slowly trying to figure out which part of the public marvin test infrastructure we can run against our test infrastructure (and then, later on, add our own tests to the public set…).
Having some kind of a defined set of “these tests belong with and pass against 4.4.0 (in the citrix QA environment)” would be a _huge_ help. Cheers, Leo On 6/26/14, 3:21 PM, "Daan Hoogland" <daan.hoogl...@gmail.com> wrote: >if it is test code it will hardly interfere with the release, If it >does it is extra important to know about it early. The only reason to >not put them in the 4.4 branch is because you don't want them in the >4.4.0 release. > >On Thu, Jun 26, 2014 at 1:33 PM, Abhinandan Prateek ><abhinandan.prat...@citrix.com> wrote: >> >> >> On 25/06/14 11:30 pm, "Daan Hoogland" <daan.hoogl...@gmail.com> wrote: >> >>>On Wed, Jun 25, 2014 at 7:58 PM, Santhosh Edukulla >>><santhosh.eduku...@citrix.com> wrote: >>>... >>>> Team uses 4.4-forward marvin to test the changes. >>>You should really not test 4.4-forward, but 4.4! >> It is mainly about testing and fixing the Marvin framework. >> Didn¹t want to interfere with the current release. >> >> -abhi >>> >> > > > >-- >Daan
