[Bug 6469] [FT] TestSuite issues

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


Pat Case <pcase@crs.loc.gov> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pcase@crs.loc.gov




--- Comment #1 from Pat Case <pcase@crs.loc.gov>  2009-02-04 21:18:35 ---
Christian,

I can address a few of these:

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

Query yields a boolean, whereas the result contains elements

--Yes. Fixed, this one and one that follows. The results now contain true.

[4] ftstaticcontext-results-q1.txt:

Result file is incorrect (superfluous: line 377-end)

--Removed. Static context queries will be replaced.

[5] ftstaticcontext-results-q2.txt:

Result file is incorrect (superfluous: line 280-end)

--Removed. Static context queries will be replaced.

[6] ftstaticcontext-results-q6.txt:

All books expected as result ('approved'/'approve' -> 'approv')

--Removed. Static context queries will be replaced.

[18] ftwildcard-q2.xq

<book number="2"> is missing

--This query looks for "site." site followed a period (not an indicator). There
is a sites. The title ends in site but does not end in a period. I don't see
"site." in Book 2.

--The language document says: The "without wildcards" option finds tokens
without recognizing wildcard indicators and qualifiers. Periods, question
marks, asterisks, plus signs, and two numbers separated by a comma, both
enclosed by curly braces, are always recognized as ordinary text characters.

--Might you have been thinking the period was an indicator or I am missing your
point?

[19] ftwildcard-q5.xq

<book number="1"> expected as result (as it contains the word "task")

--I was clearly confused about what word I was searching on, so I changed the
word in query to match the description to "site.?" That word is not in any book
for the same reasons described above, unless again I am missing oyur point.

[29] ft-3.4.5-examples-q1.xq

true expected (or lowercase option missing)

--Yes, indeed the lowercase option was missing. I added it. 

As always thanks to you Christian.

Pat


-- 
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 Wednesday, 4 February 2009 21:18:51 UTC