Author: bcarothers Date: 2010-01-05 19:36:37 -0500 (Tue, 05 Jan 2010) New Revision: 1532 Modified: trunk/dna-integration-tests/src/test/resources/tck/jdbcmeta/repositoryOverlay.properties Log: DNA-623 JDBC Metadata TCK Test Failing in Nightly Integration Build Now that the query tests are enabled, the TCK test is running XPathPosIndexTest against all of the connectors. This test has a written prerequisite (in Javadoc) that the root node have at least 3 child nodes named the same as the value of the "nodeName1" property. However, the test checks for a different precondition (more than three child nodes in total). Since the JDBC Metadata connector doesn't support same-name siblings, it cannot meet the written prerequisite, but the configured root node did have more than 3 child nodes. So the test tried to execute, but the query (which ended in [2]) couldn't possibly return values from this connector. The applied patch moves the root for the test cases to a node that only has two children, effectively bypassing this test[1]. This is actually better for most other tests since it moves the test root closer to the actual root of the repository and exposes more nodes to TCK testing. I tried to do this originally when I added the connector, but the performance was too slow. [1] - This is why the FileSystemRepositoryTCKTest didn't also break. Although it doesn't support SNS either, the root node happened to only have two children so this test was effectively bypassed for that connector as well. Modified: trunk/dna-integration-tests/src/test/resources/tck/jdbcmeta/repositoryOverlay.properties =================================================================== --- trunk/dna-integration-tests/src/test/resources/tck/jdbcmeta/repositoryOverlay.properties 2010-01-05 20:33:47 UTC (rev 1531) +++ trunk/dna-integration-tests/src/test/resources/tck/jdbcmeta/repositoryOverlay.properties 2010-01-06 00:36:37 UTC (rev 1532) @@ -5,7 +5,7 @@ javax.jcr.tck.dnaNodeTypePath=/org/jboss/dna/connector/meta/jdbc/connector-metajdbc.cnd # The fan-out from the tables node is HUGE in HSQLDB. This allows the tests to complete reasonably quickly. -javax.jcr.tck.testroot=/default/INFORMATION_SCHEMA/tables/SYSTEM_ALIASES +javax.jcr.tck.testroot=/default/INFORMATION_SCHEMA # There's only one workspace per repository for this connector right now javax.jcr.tck.workspacename=default