db-jdo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c..@apache.org
Subject svn commit: r380018 - /db/jdo/branches/2.0-rc1/tck20/COVERAGE.txt
Date Thu, 23 Feb 2006 01:47:27 GMT
Author: clr
Date: Wed Feb 22 17:47:25 2006
New Revision: 380018

URL: http://svn.apache.org/viewcvs?rev=380018&view=rev
Log:
Updated COVERAGE

Modified:
    db/jdo/branches/2.0-rc1/tck20/COVERAGE.txt

Modified: db/jdo/branches/2.0-rc1/tck20/COVERAGE.txt
URL: http://svn.apache.org/viewcvs/db/jdo/branches/2.0-rc1/tck20/COVERAGE.txt?rev=380018&r1=380017&r2=380018&view=diff
==============================================================================
--- db/jdo/branches/2.0-rc1/tck20/COVERAGE.txt (original)
+++ db/jdo/branches/2.0-rc1/tck20/COVERAGE.txt Wed Feb 22 17:47:25 2006
@@ -1,51 +1,82 @@
 TCK Coverage Document for JSR-243 Java Data Objects 2.0:
 
+TCK Overview:
+---------------
+The JDO TCK tests use the JUnit testing framework. The TCK is distributed 
+as a source tree archive containing test source and all required configuration 
+files, including the JDO metadatafiles and SQL scripts. Test build and 
+execution is driven by the maven.xml build script. The user can run the 
+full test suite, groups of tests, or individual tests. Test results and 
+configuration information are saved in a timestamped log directory.
 
 TCK Components:
 ---------------
-- RunRules.html
+- Installation instructions at db.apache.org/jdo/downloads
+- README.txt
+- Run Rules
+- maven.xml test driver
 - Test Suite
-- Signature Test
-- JUnit Harness
+- exclude list
+
+TCK Dependencies to be manually installed (documented in README.txt) :
+---------------
+- Maven 1.0.x
+- JNDI implementation
+
+TCK Dependencies  downloaded automatically by Maven:
+---------------
+- JDO2 components api20, core20, enhaner20, tck20
+- JUnit test framework
+- JPOX JDO implementation
+- Derby
+- Other third-party libraries
 
 Terminology of Metrics
 ----------------------
-- Assertion: A specific statement of functionality or behavior derived from a specification.
-  A testable assertion is one that can be validated in an implementation by testing.
+- Assertion: A specific statement of functionality or behavior derived 
+from a specification.
+  A testable assertion is one that can be validated in an implementation 
+by testing.
 - Test: A binary application (or script) comprised of one or more Test Cases.
-- Test Case: A single set of test inputs, execution conditions, and expected results
-  developed to verify an implementation's conformance with a specific assertion.
-- Specification Assertion Coverage: Ratio of all assertions tested by at least one test
+- Test Case: A single set of test inputs, execution conditions, and expected 
+results developed to verify an implementation's conformance with a specific 
+assertion.
+- Specification Assertion Coverage: Ratio of all assertions tested by at 
+least one test
   case to the total number of testable assertions defined by the specification.
-- API Coverage: Ratio of methods directly exercised by test cases to the total number
-  of methods defined by the specification.
+- API Coverage: Ratio of methods directly exercised by test cases to the 
+total number of methods defined by the specification.
 
 Coverage
 --------
-- Total testable assertions: 1154 testable assertions
-  Assertions identified through the use of hand markup
-- API Signature Coverage: 100% for all defined public and protected members and validated
-  by the signature test included with the TCK.
-- See the following HTML reports in this bundle for JBI specification and API coverage metrics:
+- Total testable assertions: 791 specification assertions, identified through 
+hand markup of the FrameMaker specification document using conditional text. 
+Chapter 18 of the specification provides an XML grammar for metadata, for 
+which separate assertions were not developed. The metadata is extensively 
+tested by a small number of tests using a number of different metadata sets.
+- Tests: 538
+- Test cases: 1158
+- Assertion coverage: 538/791 = 68%
+- API Signature Coverage: 100% for all defined public and protected members
+<>
 
 Quality Assurance
 -----------------
-- TCK was run using representative configurations of the Reference Implementation on
+- TCK was run using representative configurations of the Reference 
+Implementation on
   the following platforms:
+   * Windows 2000 Pro/Sun  J2SE 1.4.2
+   * MacOX 10.4/Sun J2SE 1.4.2
    * Red Hat Linux/Sun J2SE 1.4.2
-   * Windows XP/Sun J2SE 1.4.2
-   * MacOSX 10.4/Sun J2SE 1.4.2
-
-- Code quality was demonstrated through use of code reviews and inspections
+- TCK code quality was demonstrated through use of code reviews conducted 
+publicly on the jdo-dev@apache.org emal list
 - Documentation instructions were verified and tested
 
+
 Justification of Adequacy
 -------------------------
-As the second major release of this specification, the coverage is good and consistent
-with the coverage of similar JSRs at this level of spec maturity. Coverage variance
-is due to effects of late spec changes and the availability/cost of test development
-resources. We plan to increase coverage over the next few months and release an updated
-version of the TCK. Licensees are strongly encouraged to utilize the latest version of the
-TCK when testing the compatibility of their JDO implementation, provided the TCK is
-available, and the licensee chooses to use it, at the time of testing.
+Given the large number of assertions and metadata elements, the coverage 
+is good. 
+<>The availability of test development resources was limited.
+
 



Mime
View raw message