[Bug 17227] New: [QT3TS] fn-available-environment-variables-011

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17227

           Summary: [QT3TS] fn-available-environment-variables-011
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 3 & XPath 3 Test Suite
        AssignedTo: oneil@saxonica.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org


I think this test imposes unreasonable demands on an implementation and/or test
driver.

To quote the comments in the test: "   
<!--* In order to pass test case 11 you *either* need to set
       * an environment variable QTTEST to the
       * string value 42, *or* available-environment-variables
       * must return () indicating no variables available.

Now, a perfectly reasonable implementation might have
available-environment-variables() and environment-variable() return the values
of operating system variables as exposed using Java's System.getenv(). But if
that's the way it's implemented, then there is no way a Java test driver can
set particular environment variables to particular values. It can be done in
the shell externally to the test driver application, but that's very difficult
to achieve if, for example tests are being run in Java servlets, perhaps in
multiple processes.

It's tempting to change our implementation of environment variables so they map
to Java system properties instead of operating system variables. That would
enable us to pass this test. But I don't think we should redesign our product
in a way that helps us pass tests but does nothing for users.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Monday, 28 May 2012 22:40:35 UTC