[
https://issues.apache.org/jira/browse/HCATALOG-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487570#comment-13487570
]
Travis Crawford commented on HCATALOG-535:
------------------------------------------
Absolutely! I'm entirely for testing all changes with the rigor they deserve!
Right now its just entirely impractical to request everyone run the e2e tests
as-is. This change intends to make that easier. If we make it easier in some
other manor that totally fulfills my requirements. I just think we need to
strike that delicate balance between benefit of people submitting useful
changes and risk from those changes breaking things.
Given the current e2e framework, I think we in general benefit from making it
easy to run the e2e tests on a single dev machine. Although, if its easy in
general to run in a fully distributed manor that's also fine.
My main concern is requiring people to have some personal cluster they can test
against; that's not realistic. If you're at some major company, that means
requesting machines through some allocation team, having them on some capacity
plan, planned for in datacenter moves, etc. Its a pretty big deal to assume you
have a test cluster that meets the hcat requirements, and you need
organizational buyin. If you're some non-bigco developer you might not have the
resources to have that dedicated cluster. If we make it easy to spin up an ec2
cluster or similar that lets people easily and cheaply test their changes which
seems practical. But as soon as we demand committers have some dedicated
cluster with specific requirements, that's a pretty high bar to pass.
I'm totally in support of "awesome testing" since that's going to limit risk in
this project we chose to collectively develop. Anything that makes that easy to
me is really valuable & worth pursuing.
Other than pseudo-distributed mode where everything is setup locally, how would
we make fully-distributed mode easy to do?
> HCatalog e2e tests should run locally with minimal configuration
> ----------------------------------------------------------------
>
> Key: HCATALOG-535
> URL: https://issues.apache.org/jira/browse/HCATALOG-535
> Project: HCatalog
> Issue Type: Improvement
> Reporter: Travis Crawford
> Assignee: Travis Crawford
>
> Setting up the environment to run e2e tests is documented here:
> https://cwiki.apache.org/confluence/display/HCATALOG/How+To+Test
> Its extremely time consuming to setup because there are so many moving parts.
> Some are very machine-specific, like configuring SSH and installing MySQL for
> your platform. However, some stuff we can automate for the developer, like
> downloading, installing & configuring all the Java stuff. We should do that
> to simplify.
> Also, tests do not run from a git repo because of the svn external. This
> would be very helpful to fix. Developing with Git is WAAAAAY nicer because
> branching is so easy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
