You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mrql.apache.org by "Leonidas Fegaras (JIRA)" <ji...@apache.org> on 2014/04/13 22:29:15 UTC
[jira] [Issue Comment Deleted] (MRQL-34) Introduce junit for
testing
[ https://issues.apache.org/jira/browse/MRQL-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leonidas Fegaras updated MRQL-34:
---------------------------------
Comment: was deleted
(was: Hi Lee moon,
If you don't mind, I have proposed you to be a committer and a PPMC
member of the MRQL project. This means that you can vote on new MRQL
releases and you can submit patches to the MRQL GIT repo.
Best regards
Leonidas Fegaras
)
> 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)