W3C home > Mailing lists > Public > public-qt-comments@w3.org > October 2012

[Bug 19782] test cases using 'assert-eq' for numeric values instead of 'assert'

From: <bugzilla@jessica.w3.org>
Date: Wed, 31 Oct 2012 11:29:54 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-19782-523-psR5QS3pbx@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19782

--- Comment #9 from Sorin Nasoi <spungi@gmail.com> ---
(In reply to comment #8)
> (In reply to comment #7)
> > >"assert-eq  denotes an element whose assumption when run must equal the
> > expected test result."
> > 
> > What my copy says is:
> > 
> > "The assert element contains an XPath expression (usually a simple string or
> > numeric literal) which must be equal to the result of the test case under
> > the rules of the XPath 'eq' operator. "
> > 
> > which seems clear enough. Are you using the latest CVS copy?
> 
> I looked at this:
> http://dev.w3.org/cvsweb/~checkout~/2011/QT3-test-suite/catalog-schema.
> html?rev=1.1;content-type=text%2Fhtml#elem_assert-eq

There are some issues I see:
- the catalog-schema.xsd says what you have, that is true
- the catalog-schema.html says is not updated (so it mentions what I stated)
- the description in the catalog-schema.xsd does not account for the "empty
environment" issue I reported in bug 19783: that is the fact that the
"assert-eq" is not checked in the same environment defined for the test itself
but in a default/empty one (where math prefix is not defined for instance).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 31 October 2012 11:29:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 31 October 2012 11:29:56 GMT