[
https://issues.apache.org/jira/browse/OAK-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444801#comment-13444801
]
Thomas Mueller commented on OAK-288:
------------------------------------
> proper reporting unit test failures
If there is a test failure, what I usually do is compare the expected result
(in the src/test directory) with the result in the target directory.
> the test in sql2.txt are somewhat hard to debug individually
What I usually do to debug a test individually is move the test case to the top
of the script, so it is run first.
> QueryTests should use the NodeStore apis
> ----------------------------------------
>
> Key: OAK-288
> URL: https://issues.apache.org/jira/browse/OAK-288
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Alex Parvulescu
>
> Currently the existing oak query tests come in form of a "script" file [0]
> that contains
> - commit commands which will be executed directly against the mk.
> - select commands
> - expected results
> while this was good for fast prototyping we should refactor the tests to use
> proper unit tests.
> Arguments for refactoring:
> - overall java style unit tests, reduce the complexity of running this setup
> - proper reporting unit test failures
> - executing the commit commands directly against the mk breaks the
> {{CommitHook}} mechanism because the commits will pass unnoticed
> - proper separation of concerns - oak core should not directly reference the
> mk, it should pass through exisiting apis like the {{NodeStore}}
> [0]
> http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-core/src/test/resources/org/apache/jackrabbit/oak/query/sql2.txt?view=markup
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
