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

Lee moon soo edited comment on MRQL-34 at 3/19/14 3:25 PM:
-----------------------------------------------------------

I'm attaching a patch which implements junit based test.
This patch keeps existing antrun based test.
This patch implements some basic tests based on junit.


Summary of changes

- 'core' submodule has common test routine for Evaluator. 
src/test/java/org/apache/mrql/EvaluatorTest.java 
- 'core' submodule generates tests.jar artifact.
  'bsp', 'spark', 'mapreduce' submodule add this test test artifact to it's 
dependency.
- 'bsp', 'spark', mapreduce' submodule, each of them has 2 junit test classes, 
under (bsp|spark|mapreduce)/src/test/java/org/apache/mrql, one for in memory, 
one for local mode.




was (Author: moon):
I'm attaching a patch which implements junit based test.
This patch keeps existing antrun based test.
This patch implements some, basic test based on using junit.


Summary of changes

- 'core' submodule has common test routine for Evaluator. 
src/test/java/org/apache/mrql/EvaluatorTest.java 
- 'core' submodule generates tests.jar artifact.
  'bsp', 'spark', 'mapreduce' submodule add this test test artifact to it's 
dependency.
- 'bsp', 'spark', mapreduce' submodule, each of them has 2 junit test classes, 
under (bsp|spark|mapreduce)/src/test/java/org/apache/mrql, one for in memory, 
one for local mode.



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

Reply via email to