xproc / 1.0-test-suite Goto Github PK

Also from private email:

This probably has zero importance (and you probably already know about
this), but I noticed that the documentation of the XProc test suite
vocabulary is not really in sync with the actual schema. For instance,
the prose does not mention the following:

• the content model of the t:title element
• that you can use the @href attribute on t:test

With the intent that matching any one of them is a success.

More generally: we need to deal with insiginificant variation in test suite results.

See also http://www.w3.org/XML/XProc/2013/04/24-minutes#action07

When I upgraded to the latest HTTP Apache client, I began getting false positives on the http-request multipart tests. The problem is that the updated library sends Accept-Encoding headers that change the results but aren't actually relevant to the test.

Adding a filter step to remove the headers would focus the tests more explicitly.

From private email:

While working with XProc test suite again, I am baffled by the
expected results of test "psvi-required-001.xml" over and over again.
Clearly an XProc implementation not supporting PSVI like Calumet or
mine cannot pass this test. But running the test it always
looks like I am producing wrong results on a supported step.

In my opinion reading the results of this test would be very much
clearer, if p:declare-step in the pipeline would use
attribute "psvi-required" so not supporting implementations can fail
with err:XD0022.

Would you agree or is there a reason to have the test in the current
version I did not get?