hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Szehon Ho (JIRA)" <>
Subject [jira] [Commented] (HIVE-7254) Enhance Ptest framework config to auto-pick up list of MiniXXXDriver's test
Date Thu, 19 Jun 2014 23:20:24 GMT


Szehon Ho commented on HIVE-7254:

Thanks, property file would work fine for Ptest framework.  The refactoring of normal build
process can be done as a first change.  The PTest framework today generates cmds like "mvn
test -Dtest=TestMiniTezCliDriver -Dqfile=$batch1" using its own property file, and will continue
to work.

The actual Ptest framework class is checked into the hive repo at:  [|].
 It runs against the Ptest conf file "" (attached).  As a second step,
we can replace the hard-coded test names there with references to the new property file, and
have TestParser read those.

I can take a look at this, but if anyone is interested, build instructions for Ptest framework
are at : [README|].  In
development, I usually run TestParser locally against the file to verify the generated-batches,
for example see [|].

> Enhance Ptest framework config to auto-pick up list of MiniXXXDriver's test
> ---------------------------------------------------------------------------
>                 Key: HIVE-7254
>                 URL:
>             Project: Hive
>          Issue Type: Test
>          Components: Testing Infrastructure
>            Reporter: Szehon Ho
>            Assignee: Szehon Ho
>         Attachments:
> 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
> It would be nice if both got their information the same way.

This message was sent by Atlassian JIRA

View raw message