[
https://issues.apache.org/jira/browse/MRQL-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941715#comment-13941715
]
Leonidas Fegaras commented on MRQL-34:
--------------------------------------
Same output implies same resulting values, but not necessarily the other way
around. But instead of comparing the output of a query with the expected output
in a file, you can actually parse and evaluate the expected output from the
file and compare its value with the query result. For most queries, it doesn't
make much difference. But it makes a difference when you compare multisets
(bags): for example, {1,2} must be equal to {2,1}. So don't use equals to
compare values of type bag(t). You should define your own bag equality.
Anyway, you can go ahead and use both approaches: you can hardwire the simple
queries from core_1.mrql and joins_1.mrql inside the code and you can use the
other method for the rest.
> 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)
