Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airavata.apache.org
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
Subject: Re: Airavata Release Testing
From: Suresh Marru <smarru@apache.org>
In-Reply-To: 
 <CAKUcLKbV1w1ic+8Pq0TXkVi4vBrTskCydUHQ4wetD0HobhuSpw@mail.gmail.com>
Date: Thu, 21 Nov 2013 14:20:04 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <027ED02C-8442-436A-81D0-3FA28D7133F4@apache.org>
References: 
 <CAKUcLKbV1w1ic+8Pq0TXkVi4vBrTskCydUHQ4wetD0HobhuSpw@mail.gmail.com>
To: Airavata Dev <dev@airavata.apache.org>

One more reason for automated testing:
* Humans are lazy by nature :)

+ 1 for everything.=20

Suresh

On Nov 21, 2013, at 2:12 PM, Amila Jayasekara <thejaka.amila@gmail.com> =
wrote:

> Hi Raman,
>=20
> Thank you for initiating this [1]. This list [1] is great.
> =20
> I have few comments related to verifying samples.
>=20
> It will be really great if we can automate most of these testing. =
Ideally we should only do UI testing manually (Maybe we can automate =
that too). Further we need to automate real scenarios (like running job =
against trestles/stampede)
>=20
> I see automation is necessary due to following reasons;
>=20
> 1. Humans are not perfect
> 2. We have lot of things in our minds so we are always eager to finish =
one thing and go to next. Therefore high chance we miss something. =
Further we dont have a way to assure that release manager did all the =
verifications.
> 3. We dont need to wait till release time to figure out something is =
broken.
> 4. We are a small team is small. Therefore we need to automate as much =
as possible. Infact that is the way most of the apache projects do.
>=20
> [1] =
https://cwiki.apache.org/confluence/display/AIRAVATA/Airavata+Release+Test=
ing
>=20
> Thanks
> Amila