RE: XForms 1.1 test suite issues

Without looking into the details, this looks like just another agenda item 
in the new year.  As per current charter and proposed new charter, 
maintenance of the test suite is an important component of our work.  We 
had a fantastic round of improvements recently thanks largely to your 
validator work and Joern's work on Chiba as well as some work we've been 
doing in Ubiquity XForms.  We still have a few more issues from Joern as 
well as this one now. 

Generally, the test suite could use more work in a number of areas.  We 
could continue to improve the coverage of what is tested.  I have some 
action items to add a few more specific tests, but frankly we could use a 
thorough scrub of the spec against the test suite to ensure we really do 
have all the technical requirements captured in tests.  Of course, we'd 
have to do this as a "second edition" test suite so that we avoid a 
numerical disconnect between the current test suite and the implementation 
reports.  FWIW, I think revising the current tests is acceptable even 
though it may improve or detract from an implementers results relative to 
the current reports.  There is really no harm in improvement, and in the 
case of a new failure, the implementer should feel more urgently obligated 
to patch an implementation to fix any defects uncovered by the revised 
test.  But adding tests seems to be the stuff of a new edition. 

And once we begin thinking in terms of a second edition test suite, I 
think it would be worthwhile spending some time addressing the concerns 
raised about how hard it has been to automate testing for the current 
tests.  Offhand I don't really know what specific changes are needed, so 
it is a conversation worth having, though I wouldn't want it to stand in 
the way of creating new tests.

Cheers,
John M. Boyer, Ph.D.
STSM, Interactive Documents and Web 2.0 Applications
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com 

Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
Blog RSS feed: 
http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw





From:
"Klotz, Leigh" <Leigh.Klotz@xerox.com>
To:
John Boyer/CanWest/IBM@IBMCA
Cc:
<public-forms@w3.org>
Date:
12/17/2009 10:40 AM
Subject:
RE: XForms 1.1 test suite issues



How about this error:
 
11.1.a.xhtml:8:65: error: attribute "soap:encodingStyle" not allowed here; 
expected attribute "dir", "lang", "version" or "xml:lang"
 
I looked around a bit and don't see why soap:encodingStyle belongs on the 
xhtml:html element.  SOAP asks for it on the SOAP header, and XForms 1.1 
doesn't list it at all in http://www.w3.org/TR/xforms11/#SOAP
 
Leigh.

From: John Boyer [mailto:boyerj@ca.ibm.com] 
Sent: Wednesday, December 16, 2009 5:22 PM
To: Klotz, Leigh
Cc: public-forms@w3.org
Subject: RE: XForms 1.1 test suite issues


Yes, for some reason 5.2.1.c still had the xforms::byte in it, where I 
thought that had been fixed.  I have just fixed it and updated it, 
including the zip file. 

Also, we discovered that test 11.9.4.b needed a further adjustment because 
it was counting on an xforms-submit-error handler running on a replace all 
submission.  I changed to a replace none submission since the test is 
looking for an xforms-submit-error in order to be successful.  No 
replacement functionality is actually needed to determine whether or not 
the file has been deleted.  I also updated the zip file to include this 
revision. 

For all tests revised recently, esp. today, we have verified that they 
work in Ubiquity XForms, so we believe they are all good revisions at this 
point. 

Cheers, 
John M. Boyer, Ph.D.
STSM, Interactive Documents and Web 2.0 Applications
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com 

Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
Blog RSS feed: 
http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw




From: 
"Klotz, Leigh" <Leigh.Klotz@xerox.com> 
To: 
<public-forms@w3.org> 
Date: 
12/16/2009 04:19 PM 
Subject: 
RE: XForms 1.1 test suite issues




With today's updates after the Teleconference and Editorial Meeting and 
John and Charlie's changes, here is are the three remaining validation 
errors: 
3.3.1.d3.xhtml:16:55: error: value of attribute "version" is invalid; 
token "number1engage" invalid; must be a string matching the regular 
expression "[1-9]\d*\.\d+"
5.2.1.c.xhtml:59:57: error: value of attribute "type" is invalid; must be 
an XML QName
3.3.1.d3.xhtml.xhtml:8:65: error: attribute "soap:encodingStyle" not 
allowed here; expected attribute "dir", "lang", "version" or "xml:lang"

Here is my analysis: 
3.3.1.d3.xhtml intentionally not valid. 
5.2.1.c.xhtml appears to still be in progress by Charlie and John. 
3.3.1.d3.xhtml is an XHTML RNC schema issue, not an XForms issue and I'm 
not familiar with the use of xhtml:html/@soap:encodingStyle in XHTML. 
Leigh.

-----Original Message-----
From: public-forms-request@w3.org [mailto:public-forms-request@w3.org] On 
Behalf Of Klotz, Leigh
Sent: Friday, December 11, 2009 10:26 AM
To: public-forms@w3.org
Subject: XForms 1.1 test suite issues

I've uncovered the following validation errors in the XForms 1.1 test 
suites in the process of producing and testing the Relax NG XHTML+XForms 
integration. 

I have recommendations for most, but a few require special examination:
- There are two tests that I believe are no longer used, and are likely 
present but not referenced. 
- There is a test with binding exceptions that I don't understand.
- There is a test using choices with no contained items that I believe we 
should consider separately.

Fetch the test suite from 
http://www.w3.org/MarkUp/Forms/Test/XForms1.1/Edition1/zip/TestCases11.zip 
and save this file in the same directory.  Unzip both and the links from 
this document will take you to the test cases.

Leigh.