[
https://issues.apache.org/jira/browse/HIVE-7254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076475#comment-14076475
]
Szehon Ho commented on HIVE-7254:
---------------------------------
Yes that sounds good to me, Lefty. I think we can go with "MiniDriver and
Beeline tests" in the links , to have less maintenance cost when we add more
miniDriver tests, as we might have MiniSparkDriver later, if that is ok.
Good point about Beeline driver tests, it seems is separate enough that its not
included in miniDriver tests, and we should include it to be clear. Although
now that you mention it, I'm not sure if beeline driver tests are properly
documented anywhere. Right now they are not run by default during build (need
to specify a flag), and ideally we should have some mention of how to run them,
even though I kind of doubt developers do that exercise normally.
> Enhance Ptest framework config to auto-pick up list of MiniXXXDriver's test
> ---------------------------------------------------------------------------
>
> Key: HIVE-7254
> URL: https://issues.apache.org/jira/browse/HIVE-7254
> Project: Hive
> Issue Type: Test
> Components: Testing Infrastructure
> Reporter: Szehon Ho
> Assignee: Szehon Ho
> Attachments: trunk-mr2.properties
>
>
> Today, the Hive PTest infrastructure has a test-driver configuration called
> "directory", so it will run all the qfiles under that directory for that
> driver. For example, CLIDriver is configured with directory
> "ql/src/test/queries/clientpositive"
> However the configuration for the miniXXXDrivers (miniMRDriver,
> miniMRDriverNegative, miniTezDriver) run only a select number of tests under
> "directory". So we have to use the "include" configuration to hard-code a
> list of tests for it to run. This is duplicating the list of each
> miniDriver's tests already in the /itests/qtest pom file, and can get out of
> date.
> It would be nice if both got their information the same way.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
