[ 
https://issues.apache.org/jira/browse/HIVE-18495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16334024#comment-16334024
 ] 

Zoltan Haindrich commented on HIVE-18495:
-----------------------------------------

[~asherman] the patch has a simple sample testcase; but for a real life 
example; I'm using it in my wip branch 
[here|https://github.com/kgyrtkirk/hive/blob/79acdc7a65c3e01547178e38ee3fbad503477048/ql/src/test/org/apache/hadoop/hive/ql/plan/mapping/TestCounterMapping.java#L138].
 

> JUnit rule to enable Driver level testing
> -----------------------------------------
>
>                 Key: HIVE-18495
>                 URL: https://issues.apache.org/jira/browse/HIVE-18495
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Testing Infrastructure
>            Reporter: Zoltan Haindrich
>            Assignee: Zoltan Haindrich
>            Priority: Major
>         Attachments: HIVE-18495.01.patch
>
>
> I've tried to write a case for a sophisticated check...it worked so well that 
> I've started using it and eventually created a junit rule to make it easier 
> to reuse
> Currently it takes ~15-25sec to run a test case with this framework (from 
> which most of the time is the launch time of all kind of stuff which are 
> needed to run a driver command).
> * enable to write JUnit tests which has access to the {{IDriver}} level
> * leave out the cli-driver; it sometimes causes problems
> * write tests at the {{ql}} module
> * it should also work from the IDE without changing anything
> Note: JUnit 5 would be great for this task; but unfortunately junit5 needs 
> maven-surefire 2.19.1 ; which causes all kinds of problems for hive devs 
> using idea...so that's not an option.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to