On Thu, Jun 06, 2013 at 10:50:03AM +0530, Prasanna Santhanam wrote:
> Hi,
>
> I would like to get everyone's opinions on the timeline and policies
> for bringing in automated tests into the repo. Integration tests are
> written in marvin by various people today within and without Citrix.
> Similar
> -Original Message-
> From: Joe Brockmeier [mailto:j...@zonker.net]
> Sent: Thursday, June 06, 2013 5:14 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] code-freeze and integration tests
>
> On Thu, Jun 6, 2013, at 12:20 AM, Prasanna Santhanam wrote:
&g
0 PM
> To: CloudStack Dev
> Subject: [DISCUSS] code-freeze and integration tests
>
> Hi,
>
> I would like to get everyone's opinions on the timeline and policies for
> bringing in automated tests into the repo. Integration tests are written in
> marvin by various people toda
On Thu, Jun 6, 2013, at 12:20 AM, Prasanna Santhanam wrote:
> I would like to get everyone's opinions on the timeline and policies
> for bringing in automated tests into the repo. Integration tests are
> written in marvin by various people today within and without Citrix.
> Similar to docs I'd like
On Thu, Jun 6, 2013 at 1:20 AM, Prasanna Santhanam wrote:
> Hi,
>
> I would like to get everyone's opinions on the timeline and policies
> for bringing in automated tests into the repo. Integration tests are
> written in marvin by various people today within and without Citrix.
> Similar to docs I
help to bring automation to the
same level as code base.
-Original Message-
From: Prasanna Santhanam [mailto:t...@apache.org]
Sent: Wednesday, June 05, 2013 10:20 PM
To: CloudStack Dev
Subject: [DISCUSS] code-freeze and integration tests
Hi,
I would like to get everyone's opinions o
Hi,
I would like to get everyone's opinions on the timeline and policies
for bringing in automated tests into the repo. Integration tests are
written in marvin by various people today within and without Citrix.
Similar to docs I'd like to propose that tests can be committed to the
repository beyon
