[
https://issues.apache.org/jira/browse/MRQL-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonidas Fegaras updated MRQL-4:
--------------------------------
Attachment: build.xml
Makefile
mrql-env.sh
MRQL-4.patch
> Create a testbed for MRQL queries using JUnit
> ---------------------------------------------
>
> Key: MRQL-4
> URL: https://issues.apache.org/jira/browse/MRQL-4
> Project: MRQL
> Issue Type: New Feature
> Affects Versions: 0.9.0
> Environment: Apache Ant
> Reporter: Leonidas Fegaras
> Assignee: Leonidas Fegaras
> Attachments: build.xml, Makefile, MRQL-4.patch, mrql-env.sh
>
>
> We need to create a framework for performing tests on various MRQL queries
> before the first release. Since we haven't used maven for building MRQL yet,
> I think we can do these tests using JUnit in the Ant build.xml. I do not have
> any experience with JUnit yet, but I was thinking to create a test framework
> similar to Hive's:
> * we can create the directories tests/queries to keep MRQL queries,
> tests/data for input data, and tests/results to keep the expected query
> results
> * allow a committer to add new queries/data/results incrementally
> * be able to execute all tests in all modes using Ant: memory, MapReduce, and
> BSP modes
> * we should require that every patch must pass all tests before commit
> Questions: Is JUnit reasonable for these tasks? Is it better to use maven?
> (we may have to wait longer for this)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
