Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of min.chen@citrix.com
 designates 66.165.176.89 as permitted sender)
From: Min Chen <min.chen@citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Wed, 27 Feb 2013 17:19:00 -0800
Subject: Re: [MERGE] Merge vim51_win8 to master (Vmware SDK upgrade)
Thread-Topic: [MERGE] Merge vim51_win8 to master (Vmware SDK upgrade)
Thread-Index: Ac4VUZdTXbRtM0A2SlG5czpehAX4pA==
Message-ID: <CD53EF0E.9E61%min.chen@citrix.com>
In-Reply-To: <20130227205519.GH81779@USLT-205755.sungardas.corp>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.1.130117
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

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.

Thanks
-min

On 2/27/13 12:55 PM, "Chip Childers" <chip.childers@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?
>