Thanks Chip. If there is no other objection, I will do the merge this afternoon.
-min On 2/28/13 1:04 PM, "Chip Childers" <chip.child...@sungard.com> wrote: >On Wed, Feb 27, 2013 at 05:19:00PM -0800, Min Chen wrote: >> Honestly speaking, the reason that I didn't run existing marvin test >>suite >> against my local setup is that I myself is not familiar with Marvin test >> framework and don't know how to cook up a marvin test setup for Vmware. >> But IMHO, run marvin test against my local setup does not add extra >>values >> to those manual tests I have done. To really enable automated >>integration >> testing for this feature, we need to have CI environment for Vmware in >> place. >> > >So I'm +1 on the merge, but wanted to raise the concern that testing >manually (not considering the test environment) is generally brittle and >easily forgotten. IMO, we should all learn how to create scenarios for >Marvin. > >Thanks for humoring me Min. > >> Thanks >> -min >> >> On 2/27/13 12:55 PM, "Chip Childers" <chip.child...@sungard.com> wrote: >> >> >On Wed, Feb 27, 2013 at 09:14:44AM -0800, Min Chen wrote: >> >> We don't have devcloud or devcloud-kvm for vmware. To use marvin >>tests, >> >>we >> >> need to set up dedicated vCenter setup, not sure if we have that. >> > >> >Devcloud implies that I was asking about a CI environment. I'm >>actually >> >just asking about the test process itself. Why not drive a Marvin test >> >suite against your setup? >> > >> >>
