You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "Yoonmin Nam (JIRA)" <ji...@apache.org> on 2014/07/09 08:44:04 UTC

[jira] [Assigned] (TAJO-876) Remove the use of direct paths in TestSQLAnalyzer

     [ https://issues.apache.org/jira/browse/TAJO-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yoonmin Nam reassigned TAJO-876:
--------------------------------

    Assignee: Yoonmin Nam

>  Remove the use of direct paths in TestSQLAnalyzer
> --------------------------------------------------
>
>                 Key: TAJO-876
>                 URL: https://issues.apache.org/jira/browse/TAJO-876
>             Project: Tajo
>          Issue Type: Improvement
>            Reporter: Hyunsik Choi
>            Assignee: Yoonmin Nam
>            Priority: Trivial
>              Labels: newbie
>
> Most of the unit tests in TestSQLAnalyzer use direct path for SQL files and the expected result. It causes errors when we run the unit tests via IDE without specifying the correct base dir.
> Example:
> {code}
> @Test
>   public void testSelect1() throws IOException {
>     String sql = FileUtil.readTextFile(new File("src/test/resources/queries/default/select_1.sql"));
>     parseQuery(sql);
>   }
> {code}
> The recent unit test uses an utility method for tests as follows:
> {code}
> @Test
>   public void windowFunction7() throws IOException {
>     assertParseResult("window7.sql", "window7.result");
>   }
> {code}
> The main purpose of this issue is to change existing problematic unit tests to use the utility method {{assertParseResult()}}.



--
This message was sent by Atlassian JIRA
(v6.2#6252)