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 ivavladimir@gmail.com designates
 66.249.82.198 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:references;
        b=XJoM6Enfryl+cBgK09fD8GDuPart4d58hosDKElZCyukYoiZWezjWI6NqPI8nUFL3XH0Tas7qwT+DXcZSbwP3p5TxKeSB/hD8sYjSwCMK8JTl4oogLJanmYPhxrb1eeUhYJsOm2lSr9WjDj4D0PmZFpzmP0UASmqK0x2m42MCaY=
Message-ID: <7273946b0607260305w358c8611q9141290458cc9fa7@mail.gmail.com>
Date: Wed, 26 Jul 2006 17:05:39 +0700
From: "Vladimir Ivanov" <ivavladimir@gmail.com>
To: harmony-dev@incubator.apache.org
Subject: Re: [testing] Peace (was: Re: svn commit: r419522 - in
 /incubator/harmony/enhanced/classlib/trunk/modules/nio: .classpath build.xml
 make/hyproperties.xml src/test/java/common/ src/test/java/common/org/
 src/test/java/linux/ src/test/java/org/ src/test
In-Reply-To: <7273946b0607260253m1a91b11rae75c0c034cdfdd0@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_90240_21477683.1153908339521"
References: <7273946b0607240654i7e951260x1e803ce476821982@mail.gmail.com>
	 <2c9597b90607240825h5e924809ucaaa19328c12d179@mail.gmail.com>
	 <7273946b0607260253m1a91b11rae75c0c034cdfdd0@mail.gmail.com>

------=_Part_90240_21477683.1153908339521
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

The more I work with our tests the more I see that managing tests via
directory layout is worse than using metadata.

I thought about three more characteristics we might want to mark-up tests
with:
    - Platform-specific unit tests
    - Harmony implementation test vs. API tests
    - Broken buggy tests
    - Tests failing due to bug in implementation
    - [Potentially in future] type of test - unit, functional, stress,
reliability, etc.
    - [Potentially in future] regression test
    - Each of the listed above can be:
        - OS-specific
        - Processor architecture-specific
NEW =96 Test should be executed only in separate JVM

NEW =96 Long running test

NEW =96 Non-re-enterable test

We already have "only in separate VM" tests, for example
org/apache/harmony/logging/tests/java/util/logging/LogManagerTest.java

*Long running=96 we might want to mark-up such tests sometime later when we
have long-running tests and do not want to execute them in quick
pre-integration testing for example.

*Non-re-enterable =96 we might want to mark-up such tests when we try to
re-use unit tests in unusual modes =96 for example for reliability or stres=
s
testing purposes.

thanks, Vladimir

------=_Part_90240_21477683.1153908339521--