[
https://issues.apache.org/jira/browse/MRQL-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13969502#comment-13969502
]
Leonidas Fegaras commented on MRQL-34:
--------------------------------------
The patched source doesn't compile because the class QueryTest is missing from
the patch. Could you please create and attach the path again?
Here are the mvn errors:
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR]
/home/fegaras/mrql-release/junit/mapreduce/src/test/java/org/apache/mrql/MapReduceQueryLocalModeTest.java:[8,50]
cannot find symbol
symbol: class QueryTest
[ERROR]
/home/fegaras/mrql-release/junit/mapreduce/src/test/java/org/apache/mrql/MapReduceQueryInMemoryTest.java:[5,49]
cannot find symbol
symbol: class QueryTest
[ERROR]
/home/fegaras/mrql-release/junit/mapreduce/src/test/java/org/apache/mrql/MapReduceQueryLocalModeTest.java:[10,17]
cannot find symbol
symbol: variable super
location: class org.apache.mrql.MapReduceQueryLocalModeTest
[ERROR]
/home/fegaras/mrql-release/junit/mapreduce/src/test/java/org/apache/mrql/MapReduceQueryLocalModeTest.java:[14,9]
method does not override or implement a method from a supertype
[ERROR]
/home/fegaras/mrql-release/junit/mapreduce/src/test/java/org/apache/mrql/MapReduceQueryInMemoryTest.java:[7,9]
method does not override or implement a method from a supertype
[INFO] 5 errors
> 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)
