[
https://issues.apache.org/jira/browse/MRQL-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13972865#comment-13972865
]
Leonidas Fegaras commented on MRQL-34:
--------------------------------------
I don't know your code, but if I have :
public void setUp() throws Exception {
Config.compile_functional_arguments = false;
createEvaluator();
Translator.global_reset();
}
I get the following errors:
Tests in error:
testCore1ArrayPlus(org.apache.mrql.MapReduceEvaluatorInMemoryTest)
testCore1TupleIndex(org.apache.mrql.MapReduceEvaluatorInMemoryTest)
testCore1Cast(org.apache.mrql.MapReduceEvaluatorInMemoryTest)
testCore1Math(org.apache.mrql.MapReduceEvaluatorInMemoryTest)
testCore1Variable(org.apache.mrql.MapReduceEvaluatorInMemoryTest)
testCore1Array(org.apache.mrql.MapReduceEvaluatorInMemoryTest)
testCore1Range(org.apache.mrql.MapReduceEvaluatorInMemoryTest)
Tests run: 54, Failures: 0, Errors: 7, Skipped: 0
If I remove createEvaluator(), I will get:
Tests run: 54, Failures: 0, Errors: 0, Skipped: 0
> 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-34_b.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)
