[
https://issues.apache.org/jira/browse/MRQL-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lee moon soo updated MRQL-34:
-----------------------------
Attachment: MRQL-34_a.patch
I apologize for long silence. My company was in last step to release new
product.
I attached new patch, which should be applied without previous patch.
The patch is not complete.
If you see mapreduce/src/test/java/org/apache/mrql/*Test.java,
You'll see four classes, Two for hardwiring-way, another two for generic way
(with tests/queries/*.mrql files)
The problem i was facing in generic way is, it suppose to redirect System.out
to file and compare the files between two modes (In Memory, Local). The output
is not always the same, while each mode print different debug/info messages
while processing.
> Introduce junit for testing
> ---------------------------
>
> Key: MRQL-34
> URL: https://issues.apache.org/jira/browse/MRQL-34
> Project: MRQL
> Issue Type: Improvement
> Reporter: Lee moon soo
> Attachments: MRQL-34.patch, MRQL-34_a.patch
>
>
> MRQL has testcase and it's run as java standalone application by
> org.apache.mrql.Test.
> The Test class Invoked by maven antrun plugin at test phase
> and then load the queries and generate result and compare with the previous
> result (if result exists)
> If junit runs those test case instead of antrun, it'll give some advantages
> 1. More common ways to adding / running test in Java
> 2. Once CI is setup, junit produces information for CI about details of test.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
