[Bug 6665] New: [FT] Test Suite Bugs

http://www.w3.org/Bugs/Public/show_bug.cgi?id=6665

           Summary: [FT] Test Suite Bugs
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Platform: All
               URL: http://basex.org
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Full Text 1.0
        AssignedTo: jim.melton@acm.org
        ReportedBy: christian.gruen@gmail.com
         QAContact: public-qt-comments@w3.org


Dear all,

thanks again for your efforts. I've once more debugged the current test suite:

[1] FTContent-complex1.xqy ...

File suffixes should be changed to .xq


[2] ft-3.2-examples-q5.xq:

Still an open issue (see bug 6469); I'd propose a small scoring value (to cover
more implementations) and the 'inspect' attribute.


[3] ft-3.3-examples-q1.xq:

Still open (6469)


[4] ft-3.4.4-examples-q2.xq

Expected Result: boolean value (true)


[5] examples-362-4.xq

I wouldn't expect any results for [. ftcontains "efficient" ftand ftnot "and"
window 2 words] as "and" directly follows the term "efficient" - but I might be
wrong


[6] examples-363-4.xq

The result contains the <book> element instead of the <title>


[7] examples-363-5.xq

Result is empty; I'd expect a boolean result.


[8] examples-364-2.xq

I would have expected "false" as result as no typical sentence delimiter is
found here (such as a period).


[9] ftstaticcontext-q6.xq

Book number 3 is missing in the result.


[10] /ftstaticcontext-q7.xq

No error expected here as FT-Option is in first part of prolog. (In case of an
error, I wouldn't expect FTST0001, but XPST0003).


[11] FTPrimary-FTWords-q1.xq

Wrong results (expected: <p>It is a static ...</p> and
<p>The order in ...</p>)


[12] FTPrimary-FTExtensionSelection-q1.xq

Wrong result (expected: <p>It is a static ...<p>)


[13] FTPrimary-FTWords-anyword-q4a.xq

9 (instead of 1) <p> results expected


[14] FTPrimary-FTWords-anyword-q4b.xq

9 (instead of 0) <p> results expected


[15] still open (see bug 6469..):

 "t is checked.<" -> "t is checked. <"
 "ue</nt>is"        ->  "ue</nt> is"
 "on</nt>produces"  ->  "on</nt> produces"


[16] FTSelection-FTTimes-q4d.xq

Second <p> element should be removed (contains "cardinality" only once)


[17] FTNot-q1.xq

Only 4 <title> elements expected (the other ones don't have a <para> element)


[18] ftcaseunconstrained-q1.xq

I would expect no results; if I got it right, the character conversion is only
applied to the query string (I'm just interested: can you explain why the
lowercase/uppercase options were introduced to the standard?).


[19] FTPosFilter-q2.xq

I would expect 'false' as terms are not ordered.


[20] FTPosFilter-q4.xq

Maybe I misinterepret this one, but I would expect 'false' as distance isn't 0
words.


[21] FTPosFilter-q5.xq / FTPosFilter-q6.xq

'false' expected (words are in same sentence)


[22] FTWindow-words3.xq

$x should at least be 4


[23] FTWindow-words4.xq

..is the same as FTWindow-words3.xq


[24] FTWindow-complexwords3.xq

"window 2 words" expected


[25] FTWindow-complexwords4.xq

"window 31 words" expected


[26] FTWindow-sentences1.xq / FTWindow-paragraphs1.xq

"window 2 ..." expected


[27] FTWindow-sentences3.xq / FTWindow-paragraphs3.xq

$x := 2 expected


[28] FTDistance-complexwords2.xq

<title>Ninja Coder</title> expected as result


[29] ftstaticcontext-q5.xq

I would expect an error here as both "case sensitive" and "case insensitive"
are specified (but, as usual, I can easily be wrong).


[30] ft-3.4.1-examples-q1.xq

FTST0009 expected instead of FTST0013.


[31] FTContent-and1.xq

Wrong syntax: "content.]"


[32] FTIgnore-q...

"ignore" queries should support FTST0007 as alternative result.


Best,

Christian, BaseX Team 
http://www.basex.org


-- 
Configure bugmail: http://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 Sunday, 8 March 2009 22:39:22 UTC