You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beehive.apache.org by he...@apache.org on 2004/10/12 04:18:51 UTC

svn commit: rev 54643 - in incubator/beehive/trunk/site: build/site build/site/dtd build/site/dtd/gtlf src/documentation/content/dtd src/documentation/content/dtd/gtlf src/documentation/content/xdocs

Author: heathers
Date: Mon Oct 11 19:18:50 2004
New Revision: 54643

Added:
   incubator/beehive/trunk/site/build/site/dtd/
   incubator/beehive/trunk/site/build/site/dtd/gtlf/
   incubator/beehive/trunk/site/build/site/dtd/gtlf/gtlf-config-2.0.dtd
   incubator/beehive/trunk/site/src/documentation/content/dtd/
   incubator/beehive/trunk/site/src/documentation/content/dtd/gtlf/
   incubator/beehive/trunk/site/src/documentation/content/dtd/gtlf/gtlf-config-2.0.dtd
Modified:
   incubator/beehive/trunk/site/build/site/reference.html
   incubator/beehive/trunk/site/build/site/webservices.html
   incubator/beehive/trunk/site/src/documentation/content/xdocs/webservices.xml
Log:
Added dtd.  Updated WSM page.

Added: incubator/beehive/trunk/site/build/site/dtd/gtlf/gtlf-config-2.0.dtd
==============================================================================
--- (empty file)
+++ incubator/beehive/trunk/site/build/site/dtd/gtlf/gtlf-config-2.0.dtd	Mon Oct 11 19:18:50 2004
@@ -0,0 +1,183 @@
+<!-- testlog.dtd -->
+
+<!ELEMENT description (#PCDATA)>
+
+<!-- Environment Section -->
+<!ELEMENT env-attribute EMPTY>
+<!ATTLIST env-attribute
+  name   CDATA #REQUIRED
+  value  CDATA #REQUIRED
+>
+
+<!-- Don't worry about the attributes -->
+<!ELEMENT environment (env-attribute+)>
+<!ATTLIST environment
+  hosttype  CDATA #IMPLIED 
+  primary   (TRUE|FALSE) "TRUE"
+>
+
+<!-- Output Files -->
+<!-- Don't worry about this element -->
+<!ELEMENT output-files EMPTY>
+<!ATTLIST output-files
+  filetype  CDATA "OUTPUTLOG"
+  url  		CDATA #REQUIRED
+>
+
+
+<!-- Test Case Section -->
+
+<!-- 
+	One per test result, this is the metadata about the test case 
+	testcasename  For javatest, this classname.methodname 
+	testunit 		Grouping for test cases (one level only), not scoped by any other variable 
+	testpath      descriptive value, path to the testfile (if there is one) 
+	qaowner       If used, must map to a user within the system 
+-->
+<!ELEMENT test-case (description?)>
+<!ATTLIST test-case
+  testcasename  CDATA  #REQUIRED 
+  testunit 		CDATA  #IMPLIED 
+  testpath      CDATA  #IMPLIED 
+  qaowner       CDATA  #IMPLIED 
+>
+
+
+<!-- Result Section -->
+
+<!-- Any kind of output about a test result, might include error info and stack trace -->
+<!ELEMENT output-details (#PCDATA)> 
+
+<!-- errorname Either a logical name for the error, or possibly just an exception name -->
+<!ELEMENT execution-output (output-details?)> 
+<!ATTLIST execution-output 
+	errorname CDATA #IMPLIED 
+>
+
+<!-- Ignore except for manual tests -->
+<!ELEMENT reviewer-comments  	(#PCDATA)> 
+
+<!-- Contains optional information about re-running failed tests -->
+<!ELEMENT test-replication (info?,command-line)> 
+
+<!-- 
+	Newline delimited name=value pairs, used for test point 
+    definition and comparison, therefore format should be consistent (e.g. sorted) 
+-->
+<!ELEMENT test-parameters 		(#PCDATA)> 
+
+
+<!-- Test Replication section -->
+
+<!-- Any useful information about re-running this test -->
+<!ELEMENT info 		(#PCDATA)> 
+
+<!-- Optional command lines for re-running failed tests -->
+<!ELEMENT command-line (unix,win?)>
+<!ELEMENT unix 		(#PCDATA)> 
+<!ELEMENT win 		(#PCDATA)> 
+
+
+<!-- 
+	Directly below the document element, this is the primary node for a given test in a run.  
+	Note that it may include many elements 
+	reviewstate  Don't use non-default values except ANALYZED for manual tests 
+	exectime 	 Time at which the test started, java.sql.Timestamp.toString() escape format 
+	duration     In milliseconds 
+	crlist       comma separated WebClarify CR numbers 
+	analyzer     The user who should analyze this result, 
+				 If used, must map to a user within the system 
+	
+	result       These are the different types of outcomes for a test.
+		TIMEOUT = test timed out
+		ABORT = some sort of test initialization failed
+		FRAMEABORT = the test framework failed to do something required for this test
+		SKIP = test was skipped due to a framework decision (e.g. required test failed, require utility had problems)
+		FAILURE = test failed
+		SUCCESS = test passed
+
+	isdone	   This should be removed, ignore for now 
+	logicalname  Name to easily identify an execution point within a test run 
+	resultinfo  Additional information provided about a test result (e.g. benchmark data, etc.)
+-->
+<!ELEMENT test-result (test-case, environment*, test-parameters?, execution-output?, reviewer-comments?, test-replication?, output-files*)>
+<!ATTLIST test-result
+  reviewstate  (ASSIGNED|EXECUTED|ANALYZED) "EXECUTED" 
+  exectime 	   CDATA        #REQUIRED 
+  duration     CDATA        #IMPLIED 
+  crlist       CDATA        #IMPLIED 
+  analyzer     CDATA        #IMPLIED 
+  result       (TIMEOUT|ABORT|FRAMEABORT|SKIP|FAILURE|SUCCESS|TEST_NOT_FOUND)  #REQUIRED
+  isdone	   (TRUE|FALSE) "TRUE" 
+  logicalname  CDATA        #IMPLIED 
+  resultinfo   CDATA        #IMPLIED
+>
+
+
+<!-- 
+	Header Information : 	Meta-Data about a Test Run 
+	checksum	   	Expected number of tests for a given import into Sapphire
+	resultcount	  	Expected number of tests for this GTLF file
+	execaccount 		OS user who executed this run 
+	execdate	 		java.sql.Timestamp.toString() for when this test run began 
+	harnesstype 		Descriptive field for the test harness / framework used to run the tests 
+	importinfo		Never used, supposed to have generic information about an import 
+	testruntype     		This is used to classify a test run across the product 
+	referencedPrimaryRunId	This if present would signify that the run is secondary and value corresponds to the primary run; in case its null it means its a primary run
+-->
+<!ELEMENT header-info EMPTY>
+<!ATTLIST header-info
+	checksum		CDATA #IMPLIED 
+	resultcount		CDATA #IMPLIED 
+	execaccount 		CDATA #REQUIRED 
+	execdate	 		CDATA #REQUIRED 
+	harnesstype 		CDATA #REQUIRED 
+	importinfo		CDATA #IMPLIED 
+	testruntype     		CDATA #IMPLIED
+	referencedPrimaryRunId	CDATA #IMPLIED
+>
+
+<!-- 
+	Harness Specific Data : To be reused by the harness 
+	processconfig The path to the file which is used for process management by some test frameworks
+-->
+<!ELEMENT harness-info EMPTY>
+<!ATTLIST harness-info 
+	processconfig CDATA	#IMPLIED 
+>
+
+<!-- 
+	Outermost Element : Defines a Test Run 
+	runid      	Unique id for the run across Sapphire.  Use the supplied utility. 
+	testtype 		
+	release       Must correspond to a release in the system. 
+	load          Must correspond to a load in the system, for this release. 
+	branch        Must correspond to a p4 branch in the system. 
+	string        A Sapphire semantic for frequency of execution.  
+				  Must be either 1, 2, 3, or 4.  Roughly,
+				  1 = more than once per day, like a continuous build and test
+				  2 = nightly
+				  3 = weekly
+				  4 = once per load
+	changenumber  p4 change number at which this this run occurred 
+	analyzer		Must correspond to a user in the system.  
+				  This can be overridden per test result 
+	hostname 		
+	toptestfile 	The filename (not full path) of the top testfile.  
+				  This used to help distinguish between runs, along with testruntype 
+-->
+<!ELEMENT test-log (environment?, output-files*, header-info, harness-info?, test-result+)>
+<!ATTLIST test-log
+  runid      	CDATA				 #REQUIRED 
+  testtype 		(AUTOMATED|MANUAL)   #REQUIRED 
+  release       CDATA                #REQUIRED 
+  load          CDATA                #REQUIRED 
+  branch        CDATA                #IMPLIED 
+  string        CDATA                #REQUIRED 
+  changenumber  CDATA                #IMPLIED 
+  analyzer      CDATA                #IMPLIED 
+  hostname      CDATA                #IMPLIED
+  toptestfile 	CDATA                #IMPLIED 
+  runmodifier 	CDATA                #IMPLIED 
+>
+

Modified: incubator/beehive/trunk/site/build/site/reference.html
==============================================================================
--- incubator/beehive/trunk/site/build/site/reference.html	(original)
+++ incubator/beehive/trunk/site/build/site/reference.html	Mon Oct 11 19:18:50 2004
@@ -214,22 +214,30 @@
 <ul>
 			
 <li>
+				
 <a target="_blank" href="reference/taglib/index.html">Page Flow &lt;netui&gt; Tag Reference</a>
+			
 </li>
 			<!--<li><fork href="reference/taglib/index.html">Page Flow Annotations Reference</fork></li>-->
 			
 <li>
+				
 <a target="_blank" href="/reference/classref_pageflows/index.html">Page Flow API Reference</a>
+			
 </li>
 			<!--<li><fork href="/reference/classref_controls/index.html">Controls Annotations Reference</fork></li>-->
 			
 <li>
+				
 <a target="_blank" href="/reference/classref_controls/index.html">Controls API Reference</a>
+			
 </li>
 			<!--<li><fork href="/reference/classref_wsm/index.html">Web Services Metadata Annotations Reference</fork></li>-->
 			
 <li>
+				
 <a target="_blank" href="/reference/classref_wsm/index.html">Web Services Metadata API Reference</a>
+			
 </li>
 		
 </ul>

Modified: incubator/beehive/trunk/site/build/site/webservices.html
==============================================================================
--- incubator/beehive/trunk/site/build/site/webservices.html	(original)
+++ incubator/beehive/trunk/site/build/site/webservices.html	Mon Oct 11 19:18:50 2004
@@ -212,7 +212,10 @@
 </table>
 
 
-<p>See <a target="_blank" href="http://jcp.org/en/jsr/detail?id=181">JSR 181</a> for more information</p>
+<p>
+See the <a target="_blank" href="http://wiki.apache.org/beehive/Web_20Services">WSM on the Beehive wiki</a> and the 
+<a target="_blank" href="http://jcp.org/en/jsr/detail?id=181">JSR 181 Spec</a> for more information.
+</p>
 
 
 <div class="attribution"></div>

Added: incubator/beehive/trunk/site/src/documentation/content/dtd/gtlf/gtlf-config-2.0.dtd
==============================================================================
--- (empty file)
+++ incubator/beehive/trunk/site/src/documentation/content/dtd/gtlf/gtlf-config-2.0.dtd	Mon Oct 11 19:18:50 2004
@@ -0,0 +1,183 @@
+<!-- testlog.dtd -->
+
+<!ELEMENT description (#PCDATA)>
+
+<!-- Environment Section -->
+<!ELEMENT env-attribute EMPTY>
+<!ATTLIST env-attribute
+  name   CDATA #REQUIRED
+  value  CDATA #REQUIRED
+>
+
+<!-- Don't worry about the attributes -->
+<!ELEMENT environment (env-attribute+)>
+<!ATTLIST environment
+  hosttype  CDATA #IMPLIED 
+  primary   (TRUE|FALSE) "TRUE"
+>
+
+<!-- Output Files -->
+<!-- Don't worry about this element -->
+<!ELEMENT output-files EMPTY>
+<!ATTLIST output-files
+  filetype  CDATA "OUTPUTLOG"
+  url  		CDATA #REQUIRED
+>
+
+
+<!-- Test Case Section -->
+
+<!-- 
+	One per test result, this is the metadata about the test case 
+	testcasename  For javatest, this classname.methodname 
+	testunit 		Grouping for test cases (one level only), not scoped by any other variable 
+	testpath      descriptive value, path to the testfile (if there is one) 
+	qaowner       If used, must map to a user within the system 
+-->
+<!ELEMENT test-case (description?)>
+<!ATTLIST test-case
+  testcasename  CDATA  #REQUIRED 
+  testunit 		CDATA  #IMPLIED 
+  testpath      CDATA  #IMPLIED 
+  qaowner       CDATA  #IMPLIED 
+>
+
+
+<!-- Result Section -->
+
+<!-- Any kind of output about a test result, might include error info and stack trace -->
+<!ELEMENT output-details (#PCDATA)> 
+
+<!-- errorname Either a logical name for the error, or possibly just an exception name -->
+<!ELEMENT execution-output (output-details?)> 
+<!ATTLIST execution-output 
+	errorname CDATA #IMPLIED 
+>
+
+<!-- Ignore except for manual tests -->
+<!ELEMENT reviewer-comments  	(#PCDATA)> 
+
+<!-- Contains optional information about re-running failed tests -->
+<!ELEMENT test-replication (info?,command-line)> 
+
+<!-- 
+	Newline delimited name=value pairs, used for test point 
+    definition and comparison, therefore format should be consistent (e.g. sorted) 
+-->
+<!ELEMENT test-parameters 		(#PCDATA)> 
+
+
+<!-- Test Replication section -->
+
+<!-- Any useful information about re-running this test -->
+<!ELEMENT info 		(#PCDATA)> 
+
+<!-- Optional command lines for re-running failed tests -->
+<!ELEMENT command-line (unix,win?)>
+<!ELEMENT unix 		(#PCDATA)> 
+<!ELEMENT win 		(#PCDATA)> 
+
+
+<!-- 
+	Directly below the document element, this is the primary node for a given test in a run.  
+	Note that it may include many elements 
+	reviewstate  Don't use non-default values except ANALYZED for manual tests 
+	exectime 	 Time at which the test started, java.sql.Timestamp.toString() escape format 
+	duration     In milliseconds 
+	crlist       comma separated WebClarify CR numbers 
+	analyzer     The user who should analyze this result, 
+				 If used, must map to a user within the system 
+	
+	result       These are the different types of outcomes for a test.
+		TIMEOUT = test timed out
+		ABORT = some sort of test initialization failed
+		FRAMEABORT = the test framework failed to do something required for this test
+		SKIP = test was skipped due to a framework decision (e.g. required test failed, require utility had problems)
+		FAILURE = test failed
+		SUCCESS = test passed
+
+	isdone	   This should be removed, ignore for now 
+	logicalname  Name to easily identify an execution point within a test run 
+	resultinfo  Additional information provided about a test result (e.g. benchmark data, etc.)
+-->
+<!ELEMENT test-result (test-case, environment*, test-parameters?, execution-output?, reviewer-comments?, test-replication?, output-files*)>
+<!ATTLIST test-result
+  reviewstate  (ASSIGNED|EXECUTED|ANALYZED) "EXECUTED" 
+  exectime 	   CDATA        #REQUIRED 
+  duration     CDATA        #IMPLIED 
+  crlist       CDATA        #IMPLIED 
+  analyzer     CDATA        #IMPLIED 
+  result       (TIMEOUT|ABORT|FRAMEABORT|SKIP|FAILURE|SUCCESS|TEST_NOT_FOUND)  #REQUIRED
+  isdone	   (TRUE|FALSE) "TRUE" 
+  logicalname  CDATA        #IMPLIED 
+  resultinfo   CDATA        #IMPLIED
+>
+
+
+<!-- 
+	Header Information : 	Meta-Data about a Test Run 
+	checksum	   	Expected number of tests for a given import into Sapphire
+	resultcount	  	Expected number of tests for this GTLF file
+	execaccount 		OS user who executed this run 
+	execdate	 		java.sql.Timestamp.toString() for when this test run began 
+	harnesstype 		Descriptive field for the test harness / framework used to run the tests 
+	importinfo		Never used, supposed to have generic information about an import 
+	testruntype     		This is used to classify a test run across the product 
+	referencedPrimaryRunId	This if present would signify that the run is secondary and value corresponds to the primary run; in case its null it means its a primary run
+-->
+<!ELEMENT header-info EMPTY>
+<!ATTLIST header-info
+	checksum		CDATA #IMPLIED 
+	resultcount		CDATA #IMPLIED 
+	execaccount 		CDATA #REQUIRED 
+	execdate	 		CDATA #REQUIRED 
+	harnesstype 		CDATA #REQUIRED 
+	importinfo		CDATA #IMPLIED 
+	testruntype     		CDATA #IMPLIED
+	referencedPrimaryRunId	CDATA #IMPLIED
+>
+
+<!-- 
+	Harness Specific Data : To be reused by the harness 
+	processconfig The path to the file which is used for process management by some test frameworks
+-->
+<!ELEMENT harness-info EMPTY>
+<!ATTLIST harness-info 
+	processconfig CDATA	#IMPLIED 
+>
+
+<!-- 
+	Outermost Element : Defines a Test Run 
+	runid      	Unique id for the run across Sapphire.  Use the supplied utility. 
+	testtype 		
+	release       Must correspond to a release in the system. 
+	load          Must correspond to a load in the system, for this release. 
+	branch        Must correspond to a p4 branch in the system. 
+	string        A Sapphire semantic for frequency of execution.  
+				  Must be either 1, 2, 3, or 4.  Roughly,
+				  1 = more than once per day, like a continuous build and test
+				  2 = nightly
+				  3 = weekly
+				  4 = once per load
+	changenumber  p4 change number at which this this run occurred 
+	analyzer		Must correspond to a user in the system.  
+				  This can be overridden per test result 
+	hostname 		
+	toptestfile 	The filename (not full path) of the top testfile.  
+				  This used to help distinguish between runs, along with testruntype 
+-->
+<!ELEMENT test-log (environment?, output-files*, header-info, harness-info?, test-result+)>
+<!ATTLIST test-log
+  runid      	CDATA				 #REQUIRED 
+  testtype 		(AUTOMATED|MANUAL)   #REQUIRED 
+  release       CDATA                #REQUIRED 
+  load          CDATA                #REQUIRED 
+  branch        CDATA                #IMPLIED 
+  string        CDATA                #REQUIRED 
+  changenumber  CDATA                #IMPLIED 
+  analyzer      CDATA                #IMPLIED 
+  hostname      CDATA                #IMPLIED
+  toptestfile 	CDATA                #IMPLIED 
+  runmodifier 	CDATA                #IMPLIED 
+>
+

Modified: incubator/beehive/trunk/site/src/documentation/content/xdocs/webservices.xml
==============================================================================
--- incubator/beehive/trunk/site/src/documentation/content/xdocs/webservices.xml	(original)
+++ incubator/beehive/trunk/site/src/documentation/content/xdocs/webservices.xml	Mon Oct 11 19:18:50 2004
@@ -9,7 +9,10 @@
 
 <body>
 
-<p>See <fork href="http://jcp.org/en/jsr/detail?id=181">JSR 181</fork> for more information</p>
+<p>
+See the <fork href="http://wiki.apache.org/beehive/Web_20Services">WSM on the Beehive wiki</fork> and the 
+<fork href="http://jcp.org/en/jsr/detail?id=181">JSR 181 Spec</fork> for more information.
+</p>
 
 </body>