D11907: advancedqueryparsertest: Add more tests

Stefan BrĂ¼ns noreply at phabricator.kde.org
Fri Apr 6 19:49:05 UTC 2018


bruns added a comment.


  Can you add the output of the failing tests here verbatim?

INLINE COMMENTS

> michaelh wrote in advancedqueryparsertest.cpp:264
> This test fails. "no optimization" serves as a flag, that it's expected to fail and as message why. See lines 217-219. That's why I thought of dropping it, because  D11826 <https://phabricator.kde.org/D11826> does not make it pass.
> 
> If we drop this test the `failmessage` column can be removed.

Ah, this makes it somewhat complicated ...

So the parsed query is semantically correct, only the term are not merged?
If yes, the best way here is to probably keep this row as is, but also add a check testing for the unoptimized term. The second check should then carry a comment mentioning it is only a fallback.

Anyway, please make the message somewhat more meaningful, e.g. "Fails to optimize for unknown reason, but output is semantically correct".

REPOSITORY
  R293 Baloo

REVISION DETAIL
  https://phabricator.kde.org/D11907

To: michaelh, #baloo, bruns
Cc: #frameworks, ashaposhnikov, michaelh, astippich, spoorun, ngraham, bruns, alexeymin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20180406/f6829722/attachment-0001.html>


More information about the Kde-frameworks-devel mailing list