Team, Apart\Away from breaking out marvin from cloudstack, please check the other new details provided as part of the new proposal for marvin refactoring. Your inputs out of experience are invaluable. Any new feature tests for CS will be followed with the new approach, provided if we agree to all. Pasting the proposal link one more time below.
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+Refactor Regards, Santhosh ________________________________________ From: Daan Hoogland [daan.hoogl...@gmail.com] Sent: Sunday, October 06, 2013 3:05 PM To: dev Subject: Re: [DISCUSS] Breaking out Marvin from CloudStack On Sun, Oct 6, 2013 at 8:10 PM, Animesh Chaturvedi < animesh.chaturv...@citrix.com> wrote: > > Yes and we will need to work down a backlog of scenarios before we ever > > can rely on guys like me doing that. Not because they won't but because > > there is to much to write tests for edging on the new features they > > write. Just because those tests aren't there yet. I think giving Citrix > > QA a repo to work on is fine but I would like to see it merged back at > > some point and a continued possibility to write them in the main tree. > > > [Animesh>] While I don't agree to a separate repo for tests (marvin > framework is ok) I do want to call out the proposal is not for giving > Citrix QA a repo to work on and I don't think Prasanna meant that way. > I have to apologize for the formulations I choose to express my thoughts with. I did not mean to talk of a department of a certain company donating human effort for testing to the community. I was talking of the frustration of the individuals working and how the separate repo would smoothen their workflow. The new repo is in the apache domain, no question whether the work in their is done by one person or 100 companies.
