[
https://issues.apache.org/jira/browse/HCATALOG-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487456#comment-13487456
]
Travis Crawford commented on HCATALOG-535:
------------------------------------------
I think its fair to assume all users/committers have a fully-distributed
cluster, otherwise HCatalog wouldn't be very interesting to them :) However, I
don't think we can assume users/developers can run a test harness against that
cluster. There are legitimate reasons developer are prohibited from running
test jobs against a production cluster, and not all test environments have the
full stack deployed, developers don't have permissions to make all necessary
changes, etc. Having seen situations where a lossy test initialization is
accidentally run against a production system I'm pretty conservative about
mixing dev/prod.
Testing is all about catching issues before they cause harm in production. Just
like running our unit tests is super easy, if we make running e2e tests in
pseudo-distributed mode super easy I think people will actually run them and
we'll catch more issues than a more thorough test that no one runs because its
so burdensome.
Re: complex patches, I think its totally fair for anyone to post a comment
saying "hey, I'd like to test this before it goes in," and we give everyone a
chance to run the tests they feel comfortable with. We have an internal
integration test that catches different issues than the e2e tests, and
presumably other sites have their set of integration tests. This will catch the
issues people specifically care about, instead of more general use cases the
e2e tests cover.
If e2e testing locally is super easy we could do that (along with unit tests)
before every commit. For the complex stuff, if anyone has concerns about a
patch, just ask for the chance to test too.
Thoughts?
> 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
