[
https://issues.apache.org/jira/browse/MRQL-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994663#comment-13994663
]
Leonidas Fegaras commented on MRQL-34:
--------------------------------------
The MRQL-34_d.patch addresses all the problems we discussed. To build MRQL
without testing, use:
{quote}
mvn clean install
{quote}
To build MRQL with testing, do:
{quote}
mvn -DskipTests=false clean install
{quote}
Currently, the test mismatches are printed as warnings. These are not problems
with testing, but errors(?) in evaluation. They will be addressed by other JIRA
issues.
> 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-34_c.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)
