You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mrql.apache.org by "Edward J. Yoon (JIRA)" <ji...@apache.org> on 2014/04/09 11:27:15 UTC

[jira] [Commented] (MRQL-34) Introduce junit for testing

    [ https://issues.apache.org/jira/browse/MRQL-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13963966#comment-13963966 ] 

Edward J. Yoon commented on MRQL-34:
------------------------------------

What's the progress of this issue? :-)

> 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 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)