Propchange: beehive/trunk/controls/test/common/path.properties
------------------------------------------------------------------------------
svn:eol-style = native
Modified: beehive/trunk/controls/test/infra/gtlf/gtlf-config-2.0.dtd
URL:
http://svn.apache.org/viewcvs/beehive/trunk/controls/test/infra/gtlf/gtlf-config-2.0.dtd?rev=232310&r1=232309&r2=232310&view=diff
==============================================================================
--- beehive/trunk/controls/test/infra/gtlf/gtlf-config-2.0.dtd (original)
+++ beehive/trunk/controls/test/infra/gtlf/gtlf-config-2.0.dtd Fri Aug 12
08:12:28 2005
@@ -1,183 +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
->
-
+<!-- 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
+>
+
Propchange: beehive/trunk/controls/test/infra/gtlf/gtlf-config-2.0.dtd
------------------------------------------------------------------------------
svn:eol-style = native
Modified: beehive/trunk/controls/test/infra/gtlf/xsl/ReportFormat.xml
URL:
http://svn.apache.org/viewcvs/beehive/trunk/controls/test/infra/gtlf/xsl/ReportFormat.xml?rev=232310&r1=232309&r2=232310&view=diff
==============================================================================
--- beehive/trunk/controls/test/infra/gtlf/xsl/ReportFormat.xml (original)
+++ beehive/trunk/controls/test/infra/gtlf/xsl/ReportFormat.xml Fri Aug 12
08:12:28 2005
@@ -1,116 +1,116 @@
- <!-- controls the sections that should be part of the diff report
-
- The user can specify a comma separated list of sections they area interested
- in
-
- for e.g. result-Summary,setup
-
- The sections are
-
- report-Summary
- report-summary-error-list
- result-Summary
- result-Detail
- error-Summary
- error-Detail
- files
- setup
- help
- p4-Changes
- webclarify-crs
- all - all the sections are displayed
-
- The report summary is always displayed.
-
- -->
- <xsl:param name="sections">all</xsl:param>
-
-
- <!-- controls the display of navigation tools in the diff report
- controls the navigation tools that will be available
- in the report. You can specify a comma separated list
- of the navigation tools
-
- The navigation tools are:
-
- all - all the tools are displayed
- menu - menu of the report
- toolbar - toolbar of the report
- top - top link displayed in different report
- sections
- split - Capibility to split the page horizontally
- and vertically.
-
-
- -->
- <xsl:param name="navigationTools">all</xsl:param>
- <xsl:param name="reportSummaryErrorListCount">5</xsl:param>
- <xsl:param name="reportSummaryErrorListHyperlinkPrefix">NA</xsl:param>
-
- <xsl:variable name="allTool">all</xsl:variable>
- <xsl:variable name="menuNavigationTool">menu</xsl:variable>
- <xsl:variable name="toolbarNavigationTool">toolbar</xsl:variable>
- <xsl:variable name="splitNavigationTool">split</xsl:variable>
- <xsl:variable name="topNavigationTool">top</xsl:variable>
-
- <xsl:variable name="showMenuNavigationTool"
- select="contains($navigationTools,$allTool) or
- contains($navigationTools,$menuNavigationTool)"/>
- <xsl:variable name="showToolbarNavigationTool"
- select="contains($navigationTools,$allTool) or
- contains($navigationTools,$toolbarNavigationTool)"/>
- <xsl:variable name="showSplitNavigationTool"
- select="contains($navigationTools,$allTool) or
- contains($navigationTools,$splitNavigationTool)"/>
- <xsl:variable name="showTopNavigationTool"
- select="contains($navigationTools,$allTool) or
- contains($navigationTools,$topNavigationTool)"/>
-
-
- <xsl:variable name="reportSummarySection">report-summary</xsl:variable>
- <xsl:variable
-
name="reportSummaryErrorListSubSection">report-summary-error-list</xsl:variable>
- <xsl:variable name="resultSummarySection">result-summary</xsl:variable>
- <xsl:variable name="resultDetailSection">result-detail</xsl:variable>
- <xsl:variable name="errorSummarySection">error-summary</xsl:variable>
- <xsl:variable name="errorDetailSection">error-detail</xsl:variable>
- <xsl:variable name="p4ChangesSection">p4-changes</xsl:variable>
- <xsl:variable name="webclarifyCrsSection">webclarify-crs</xsl:variable>
- <xsl:variable name="setupSection">setup</xsl:variable>
- <xsl:variable name="filesSection">files</xsl:variable>
- <xsl:variable name="helpSection">help</xsl:variable>
- <xsl:variable name="allSection">all</xsl:variable>
-
- <xsl:variable name="showReportSummarySection"
- select="contains($sections,$allSection) or
- contains($sections,$reportSummarySection)"/>
- <xsl:variable name="showReportSummaryErrorListSubSection"
- select="contains($sections,$allSection) or
-
contains($sections,$reportSummaryErrorListSubSection)"/>
- <xsl:variable name="showResultSummarySection"
- select="contains($sections,$allSection) or
- contains($sections,$resultSummarySection)"/>
- <xsl:variable name="showResultDetailSection"
- select="contains($sections,$allSection) or
- contains($sections,$resultDetailSection)"/>
- <xsl:variable name="showErrorSummarySection"
- select="contains($sections,$allSection) or
- contains($sections,$errorSummarySection)"/>
- <xsl:variable name="showErrorDetailSection"
- select="contains($sections,$allSection) or
- contains($sections,$errorDetailSection)"/>
- <xsl:variable name="showP4ChangesSection"
- select="contains($sections,$allSection) or
- contains($sections,$p4ChangesSection)"/>
- <xsl:variable name="showWebclarifyCrsSection"
- select="contains($sections,$allSection) or
- contains($sections,$webclarifyCrsSection)"/>
- <xsl:variable name="showSetupSection"
- select="contains($sections,$allSection) or
- contains($sections,$setupSection)"/>
- <xsl:variable name="showFilesSection"
- select="contains($sections,$allSection) or
- contains($sections,$filesSection)"/>
- <xsl:variable name="showHelpSection"
- select="contains($sections,$allSection) or
- contains($sections,$helpSection)"/>
+ <!-- controls the sections that should be part of the diff report
+
+ The user can specify a comma separated list of sections they area interested
+ in
+
+ for e.g. result-Summary,setup
+
+ The sections are
+
+ report-Summary
+ report-summary-error-list
+ result-Summary
+ result-Detail
+ error-Summary
+ error-Detail
+ files
+ setup
+ help
+ p4-Changes
+ webclarify-crs
+ all - all the sections are displayed
+
+ The report summary is always displayed.
+
+ -->
+ <xsl:param name="sections">all</xsl:param>
+
+
+ <!-- controls the display of navigation tools in the diff report
+ controls the navigation tools that will be available
+ in the report. You can specify a comma separated list
+ of the navigation tools
+
+ The navigation tools are:
+
+ all - all the tools are displayed
+ menu - menu of the report
+ toolbar - toolbar of the report
+ top - top link displayed in different report
+ sections
+ split - Capibility to split the page horizontally
+ and vertically.
+
+
+ -->
+ <xsl:param name="navigationTools">all</xsl:param>
+ <xsl:param name="reportSummaryErrorListCount">5</xsl:param>
+ <xsl:param name="reportSummaryErrorListHyperlinkPrefix">NA</xsl:param>
+
+ <xsl:variable name="allTool">all</xsl:variable>
+ <xsl:variable name="menuNavigationTool">menu</xsl:variable>
+ <xsl:variable name="toolbarNavigationTool">toolbar</xsl:variable>
+ <xsl:variable name="splitNavigationTool">split</xsl:variable>
+ <xsl:variable name="topNavigationTool">top</xsl:variable>
+
+ <xsl:variable name="showMenuNavigationTool"
+ select="contains($navigationTools,$allTool) or
+ contains($navigationTools,$menuNavigationTool)"/>
+ <xsl:variable name="showToolbarNavigationTool"
+ select="contains($navigationTools,$allTool) or
+ contains($navigationTools,$toolbarNavigationTool)"/>
+ <xsl:variable name="showSplitNavigationTool"
+ select="contains($navigationTools,$allTool) or
+ contains($navigationTools,$splitNavigationTool)"/>
+ <xsl:variable name="showTopNavigationTool"
+ select="contains($navigationTools,$allTool) or
+ contains($navigationTools,$topNavigationTool)"/>
+
+
+ <xsl:variable name="reportSummarySection">report-summary</xsl:variable>
+ <xsl:variable
+
name="reportSummaryErrorListSubSection">report-summary-error-list</xsl:variable>
+ <xsl:variable name="resultSummarySection">result-summary</xsl:variable>
+ <xsl:variable name="resultDetailSection">result-detail</xsl:variable>
+ <xsl:variable name="errorSummarySection">error-summary</xsl:variable>
+ <xsl:variable name="errorDetailSection">error-detail</xsl:variable>
+ <xsl:variable name="p4ChangesSection">p4-changes</xsl:variable>
+ <xsl:variable name="webclarifyCrsSection">webclarify-crs</xsl:variable>
+ <xsl:variable name="setupSection">setup</xsl:variable>
+ <xsl:variable name="filesSection">files</xsl:variable>
+ <xsl:variable name="helpSection">help</xsl:variable>
+ <xsl:variable name="allSection">all</xsl:variable>
+
+ <xsl:variable name="showReportSummarySection"
+ select="contains($sections,$allSection) or
+ contains($sections,$reportSummarySection)"/>
+ <xsl:variable name="showReportSummaryErrorListSubSection"
+ select="contains($sections,$allSection) or
+
contains($sections,$reportSummaryErrorListSubSection)"/>
+ <xsl:variable name="showResultSummarySection"
+ select="contains($sections,$allSection) or
+ contains($sections,$resultSummarySection)"/>
+ <xsl:variable name="showResultDetailSection"
+ select="contains($sections,$allSection) or
+ contains($sections,$resultDetailSection)"/>
+ <xsl:variable name="showErrorSummarySection"
+ select="contains($sections,$allSection) or
+ contains($sections,$errorSummarySection)"/>
+ <xsl:variable name="showErrorDetailSection"
+ select="contains($sections,$allSection) or
+ contains($sections,$errorDetailSection)"/>
+ <xsl:variable name="showP4ChangesSection"
+ select="contains($sections,$allSection) or
+ contains($sections,$p4ChangesSection)"/>
+ <xsl:variable name="showWebclarifyCrsSection"
+ select="contains($sections,$allSection) or
+ contains($sections,$webclarifyCrsSection)"/>
+ <xsl:variable name="showSetupSection"
+ select="contains($sections,$allSection) or
+ contains($sections,$setupSection)"/>
+ <xsl:variable name="showFilesSection"
+ select="contains($sections,$allSection) or
+ contains($sections,$filesSection)"/>
+ <xsl:variable name="showHelpSection"
+ select="contains($sections,$allSection) or
+ contains($sections,$helpSection)"/>
Propchange: beehive/trunk/controls/test/infra/gtlf/xsl/ReportFormat.xml
------------------------------------------------------------------------------
svn:eol-style = native
