On Fri, Mar 01, 2013 at 02:34:08AM +0530, Chip Childers 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. > That would be great. Simplifying the writing of marvin tests is on my plate right now. Just been waylaid by a whole bunch of other issues in the meantime.
-- Prasanna.,
