This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 430 - L3 XPath Test submission
Summary: L3 XPath Test submission
Status: RESOLVED FIXED
Alias: None
Product: DOM TS
Classification: Unclassified
Component: DOM Level 3 (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: Curt Arnold
QA Contact:
URL: http://dom-ts.bclary.com/Read-Me-Firs...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-16 14:26 UTC by Bob Clary
Modified: 2003-12-22 22:07 UTC (History)
1 user (show)

See Also:


Attachments
dom3-xpath-tests.zip (99.04 KB, application/x-zip-compressed)
2003-12-16 14:28 UTC, Bob Clary
Details
Adds willBeModified's to load statements, other schema validation fixes (124.62 KB, patch)
2003-12-19 02:48 UTC, Curt Arnold
Details
Patch to fix XPathResult_stringValue (3.75 KB, patch)
2003-12-19 14:32 UTC, Bob Clary
Details

Description Bob Clary 2003-12-16 14:26:19 UTC
I have been working on adding new tests to DOM 3 XPath. When doing so, I have
renamed and made minor edits the following existing tests created by Phillipe 

isSupported01.xml
isSupported02.xml
createNSResolver01.xml
createNSResolver02.xml
createExpression01.xml
createExpression02.xml
createExpression03.xml
createExpression04.xml
createExpression05.xml
evaluate01.xml

With the exception of these files, all other files are new and I grant Copyright
to the W3. If it is acceptable to submit this mix of files, I will send the
attached zip file to the submission list.

The tests validate and the ECMAScript tests have been tested.
Comment 1 Bob Clary 2003-12-16 14:28:35 UTC
Created attachment 115 [details]
dom3-xpath-tests.zip
Comment 2 Curt Arnold 2003-12-19 02:48:50 UTC
Created attachment 130 [details]
Adds willBeModified's to load statements, other schema validation fixes

load statements were missing willBeModified attributes.
assertSame was used to compare strings.
"dummy" was used as a namespace resolver in multiple cases
Changed append statement to use "item" attribute instead of "obj" to allow
literals.
Comment 3 Bob Clary 2003-12-19 13:01:13 UTC
Note that 

XPathResult_invalidIteratorState_ANY_TYPE.xml
XPathResult_invalidIteratorState_ANY_UNORDERED_NODE_TYPE.xml
XPathResult_invalidIteratorState_BOOLEAN_TYPE.xml
XPathResult_invalidIteratorState_FIRST_ORDERED_NODE_TYPE.xml
XPathResult_invalidIteratorState_NUMBER_TYPE.xml
XPathResult_invalidIteratorState_ORDERED_NODE_ITERATOR_TYPE.xml
XPathResult_invalidIteratorState_ORDERED_NODE_SNAPSHOT_TYPE.xml
XPathResult_invalidIteratorState_STRING_TYPE.xml
XPathResult_invalidIteratorState_UNORDERED_NODE_ITERATOR_TYPE.xml
XPathResult_invalidIteratorState_UNORDERED_NODE_SNAPSHOT_TYPE.xml
XPathResult_iterateNext_INVALID_STATE_ERR.xml
 
Should be willBeModified="true" since the test attempts to invalidate the
iterator by modifying the document.

Also, 

 createExpression01.xml
 createExpression02.xml
 createExpression03.xml
 createExpression04.xml
 createExpression05.xml
 createNSResolver01.xml
 createNSResolver02.xml
 evaluate01.xml
 evaluate02.xml
 isSupported01.xml
 isSupported02.xml

have been renamed and should be CVS removed.
Comment 4 Bob Clary 2003-12-19 14:32:56 UTC
Created attachment 132 [details]
Patch to fix XPathResult_stringValue

XPathResult.stringValue is incorrect. Attached patch corrects the error.
Comment 5 Curt Arnold 2003-12-19 16:43:04 UTC
Committed XPathResult_stringValue fix and willBeModified changes