db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "StandaloneStatus" by DagWanvik
Date Sat, 25 Mar 2006 19:49:45 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by DagWanvik:

New page:
= Status of running tests standalone =

Many tests can only be run as part of a suite. Even when tests can be run on their own, they
cannot always be run with the useprocess=''false'' setting. It is desirable that this be the
case, because it aids debugging and is also faster than running the tests in a separate process.
The table below shows a snapshot of running all tests standalone in the three frameworks,
with both useprocess=''true'' and useprocess=''false''.

The set of tests was determined by taking the union of all tests mentioned in the set of *.runall
and *.exclude files.
Obviously, not all tests are meaningful to run in all frameworks, nor standalone. This status
table just shows the full status as of the date given below. YMMV.

Date of snapshot: 2006-03-24, corresponding to svn revision 387640 on Solaris 10/x86 using
Sun's JVM 1.4.2.

The results are given by indicating one of five values for each test: 

||<#00FF00>0||for success||
||1||for test is skipped by the harness for the current framework||
||<#FF0000>2||for failure||
||<#FFFF00>3||for undetermined result||
||<#FF00FF>4||for aborted by operator (due to hang)||

Success was determined by find a .pass file in the test directory, failure was determined
by finding .fail file in the test directory, skipped was determined by finding the text "Test
skipped" in a .diff file in the test directory. Undetermined test would those tests that ran
to completion but none of the three previous outcomes could be established. 

'''''snapshot coming soon'''''

View raw message