[
https://issues.apache.org/jira/browse/HIVE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666112#action_12666112
]
Johan Oskarsson commented on HIVE-231:
--------------------------------------
The problem with adding a dependency from testreport to test is that if a test
fails it won't generate the report as mentioned above. I can't find a good way
around this, but am open to suggestions.
If you want one report per component instead of one report for the whole
project my first patch should do that for you.
Personally I would use this to make sure that new changes by me haven't broken
anything. Hive builds always fail for me as per HIVE-189 making it very hard to
see if my changes broke anything else. So in my case having one report for the
whole project makes more sense.
It's certainly possible to create an overall html file that links to the
individual reports but you'd lose the "quick overview" benefits of one big
report.
Alternatively we could add both ways of creating reports but that might be
overkill.
What do you guys think?
> Create junit reports for tests
> ------------------------------
>
> Key: HIVE-231
> URL: https://issues.apache.org/jira/browse/HIVE-231
> Project: Hadoop Hive
> Issue Type: Test
> Components: Testing Infrastructure
> Reporter: Johan Oskarsson
> Assignee: Johan Oskarsson
> Priority: Trivial
> Attachments: HIVE-231.patch, HIVE-231.patch
>
>
> Suggestion to create html junit reports for the hive tests. This would give
> developers an easier overview of what has gone wrong if the build fails then
> having to look through text files.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
