Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of santhosh.edukulla@citrix.com
 designates 103.14.252.240 as permitted sender)
From: Santhosh Edukulla <santhosh.edukulla@citrix.com>
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>, Ashutosh Kelkar
	<ashutosh@clogeny.com>, Girish Shilamkar <girish@clogeny.com>,
	Srikanteswararao Talluri <srikanteswararao.talluri@citrix.com>
CC: Prasanna Santhanam <tsp@apache.org>
Subject: Marvin Enhancement
Thread-Topic: Marvin Enhancement
Thread-Index: AQHO5RYNEFHdvModmkyh+7TqMJ6jww==
Date: Tue, 19 Nov 2013 10:56:51 +0000
Message-ID: 
 <CB688D716959224C95995F52DE5E82420EBAC61F@SINPEX01CL02.citrite.net>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

1. If tests are failing and it is already a known product issue, we should =
find a way to show it as other away from "failed". This can add some enhanc=
ements to test cases, map bugs logged to failures and only new failures awa=
y from those. If it is a known issue, the failure should report it as known=
 issue rather than failure. I believe we can add these facilitation to marv=
in.=20

2. Also, if we are to integrate test cases from some test case management s=
olution to test cases under repo, there should be mapping faciliation provi=
ded for each test case in tms to test caseid or name in tests and reverse f=
aciliation to update results for those test cases. This can be more of auto=
mated approach as an integration to test management solution i believe.

Santhosh
________________________________________
From: Ashutosh Kelkar [noreply@reviews.apache.org] on behalf of Ashutosh Ke=
lkar [ashutosh@clogeny.com]
Sent: Tuesday, November 19, 2013 5:52 AM
To: Girish Shilamkar; Srikanteswararao Talluri
Cc: Ashutosh Kelkar; cloudstack; Prasanna Santhanam
Subject: Re: Review Request 15646: CLOUDSTACK-5197: portable ip - Skipping =
the tests which are failing due to product issue

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15646/
-----------------------------------------------------------

(Updated Nov. 19, 2013, 10:52 a.m.)


Review request for cloudstack, Girish Shilamkar and SrikanteswaraRao Tallur=
i.


Changes
-------

Removing skip tag from test cases which are failing due to product issue.


Bugs: CLOUDSTACK-5197
    https://issues.apache.org/jira/browse/CLOUDSTACK-5197


Repository: cloudstack-git


Description
-------

2 test cases are failing while SSHing to the VM through portable ip. Logged=
 a product defect for this - https://issues.apache.org/jira/browse/CLOUDSTA=
CK-5196.
Skipping the test cases until the product defect is resolved.


Diffs (updated)
-----

  test/integration/component/test_portable_ip.py d397ec4

Diff: https://reviews.apache.org/r/15646/diff/


Testing
-------


Thanks,

Ashutosh Kelkar