Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of mloenko@gmail.com designates
 66.249.92.196 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=hOrpltnuWmcMlGkts8+Lu2cBAg4/qeRX/oCJWURaG+oMco0Yf8Pabo0LcWWH3CBGVCvk3VPk3xT766DbaRiL6FEsXzv+L6HQBMotwgVPEbaLPl+fnCwN1Un2oiKilMETUyc8PwK56l/u3F0IWP0c1qOBm5JrWFhe3qO18jQ8mtc=
Message-ID: <906dd82e0601260411k5dcbe5e0u372bf0f086e97503@mail.gmail.com>
Date: Thu, 26 Jan 2006 18:11:13 +0600
From: Mikhail Loenko <mloenko@gmail.com>
To: harmony-dev@incubator.apache.org, geir@pobox.com
Subject: Re: [testing] code for exotic configurations
In-Reply-To: <43D8B7D1.9030203@pobox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <906dd82e0601260338i61bc439fr708c664181dc8f20@mail.gmail.com>
	 <43D8B7D1.9030203@pobox.com>

Do you mean that for a single test that verifies 10 lines of code
working on very specific configuration I have to create a parallel test tre=
e?

What about tests that work in two different exotic configurations? Should
we duplicate them?

Thanks,
Mikhail

On 1/26/06, Geir Magnusson Jr <geir@pobox.com> wrote:
> one solution is to simply group the "exotic" tests separately from the
> main tests, so they can be run optionally when you are in that exotic
> configuration.
>
> You can do this in several ways, including a naming convention, or
> another parallel code tree of the tests...
>
> I like the latter, as it makes it easier to "see"
>
> geir
>
>
> Mikhail Loenko wrote:
> > Well let's start a new thread as this is more general problem.
> >
> > So if we have some code designed for some exotic configurations
> > and we have tests that verify that exotic code.
> >
> > The test when run in usual configuration (not exotic one) should
> > report something that would not scare people. But if one
> > wants to test that specific exotic configuration that he should be
> > able to easily verify that he successfully made required conf and
> > the test worked well.
> >
> > The following options I see here:
> > 1) introduce a new test status (like skipped) to mark those tests that
> > did not actually run
> > 2) agree on exact wording that the skipped tests would print to allow
> > grep logs later
> > 3) introduce tests-indicators that would fail when current
> > configuration disallow
> > running certain tests
> >
> > Please let me know what you think
> >
> > Thanks,
> > Mikhail Loenko
> > Intel Middleware Products Division
> >
> >
>