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 5685 - [XQTS] Some FunctX tests explitly refer to files at http://www.functx.com
Summary: [XQTS] Some FunctX tests explitly refer to files at http://www.functx.com
Status: RESOLVED FIXED
Alias: None
Product: XML Query Test Suite
Classification: Unclassified
Component: XML Query Test Suite (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Frans Englich
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-13 11:28 UTC by Oliver Hallam
Modified: 2008-06-25 16:35 UTC (History)
0 users

See Also:


Attachments

Description Oliver Hallam 2008-05-13 11:28:49 UTC
A large number of functx tests explicitly load an input document from one of the following URIs:
http://www.functx.com/input/order.xml
http://www.functx.com/input/cats.xml
http://www.functx.com/input/catalog.xml
http://www.functx.com/input/prices.xml

These documents should really be in TestSources, and passed into the tests appropriately, otherwise FODC0002 is a valid result since implementations are not required to support HTTP.
Comment 1 Frans Englich 2008-05-16 08:38:08 UTC
Correct me if I'm wrong, the tests having this problem is:

functx-fn-base-uri-4
functx-fn-base-uri-5
functx-fn-base-uri-all
functx-fn-document-uri-1
functx-fn-document-uri-all
Comment 2 Frans Englich 2008-05-16 08:40:43 UTC
Ahem, correction:

functx-fn-avg-1
functx-fn-avg-2
functx-fn-avg-3
functx-fn-avg-4
functx-fn-avg-5
functx-fn-avg-all
functx-fn-base-uri-1
functx-fn-base-uri-2
functx-fn-base-uri-3
functx-fn-base-uri-4
functx-fn-base-uri-5
functx-fn-base-uri-all
functx-fn-boolean-1
functx-fn-boolean-2
functx-fn-boolean-3
functx-fn-boolean-4
functx-fn-boolean-5
functx-fn-boolean-6
functx-fn-boolean-7
functx-fn-boolean-8
functx-fn-boolean-9
functx-fn-boolean-all
functx-fn-count-1
functx-fn-count-2
functx-fn-count-3
functx-fn-count-4
functx-fn-count-5
functx-fn-count-all
functx-fn-data-1
functx-fn-data-2
functx-fn-data-3
functx-fn-data-4
functx-fn-data-5
functx-fn-data-6
functx-fn-data-all
functx-fn-doc-available-1
functx-fn-doc-available-2
functx-fn-doc-available-all
functx-fn-document-uri-1
functx-fn-document-uri-all
functx-fn-id-all
functx-fn-idref-all
functx-fn-last-1
functx-fn-last-all
functx-fn-max-1
functx-fn-max-2
functx-fn-max-3
functx-fn-max-4
functx-fn-max-all
functx-fn-min-1
functx-fn-min-2
functx-fn-min-3
functx-fn-min-4
functx-fn-min-all
functx-fn-not-2
functx-fn-not-all
functx-fn-number-1
functx-fn-number-2
functx-fn-number-3
functx-fn-number-4
functx-fn-number-5
functx-fn-number-6
functx-fn-number-all
functx-fn-root-1
functx-fn-root-all
functx-fn-sum-1
functx-fn-sum-2
functx-fn-sum-3
functx-fn-sum-4
functx-fn-sum-5
functx-fn-sum-6
functx-fn-sum-all
functx-functx-id-from-element-1
functx-functx-id-from-element-all
functx-functx-node-kind-6
functx-functx-node-kind-all
Comment 3 Frans Englich 2008-06-25 16:35:03 UTC
I've tried to fix this in CVS. These files are generated and it's not the easiest thing to get an overview of so it's very likely I've missed something here.