[
https://issues.apache.org/jira/browse/HBASE-6201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396329#comment-13396329
]
Roman Shaposhnik commented on HBASE-6201:
-----------------------------------------
bq. I think your categorization, and my comments above are telling the same
thing, no confusion there.
Great to hear -- in that case the implementation is the next level to go to.
bq. At this point, we only need starting / stopping deamons kind of
functionality, assuming the cluster is already deployed.
bq. On the other side, if we provide a "mvn verify" in hbase-it module to run
the tests on the actual cluster, I assume BigTop can leverage this to carry out
the tests.
Basically, all that Bigtop needs is a maven artifact that we can plug in our
infrastructure. We won't be using the 'mvn verify' as it is implemented in
HBase's pom.xml but rather hooking the very same artifact to our Maven
execution framework.
Are you saying that you would like the tests themeselves to get involved in the
lifecycle of each service? Like bringing them up and down, etc?
This an area I'm really interested in providing a framework for in Bigtop. I'm
about to open up a JIRA for that with the hope that we can cook something
usable up rather quickly. The key point is that I don't want tests to have any
logic that concerns itself with ssh/etc. It needs to be a sort of an
agent-based framework that allows tests to query the topology of the cluster
and also perform actions on the nodes of that topology in a most generic sense.
> HBase integration/system tests
> ------------------------------
>
> Key: HBASE-6201
> URL: https://issues.apache.org/jira/browse/HBASE-6201
> Project: HBase
> Issue Type: Bug
> Components: test
> Affects Versions: 0.96.0
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
>
> Integration and general system tests have been discussed previously, and the
> conclusion is that we need to unify how we do "release candidate" testing
> (HBASE-6091).
> In this issue, I would like to discuss and agree on a general plan, and open
> subtickets for execution so that we can carry out most of the tests in
> HBASE-6091 automatically.
> Initially, here is what I have in mind:
> 1. Create hbase-it (or hbase-tests) containing forward port of HBASE-4454
> (without any tests). This will allow integration test to be run with
> {code}
> mvn verify
> {code}
> 2. Add ability to run all integration/system tests on a given cluster. Smt
> like:
> {code}
> mvn verify -Dconf=/etc/hbase/conf/
> {code}
> should run the test suite on the given cluster. (Right now we can launch some
> of the tests (TestAcidGuarantees) from command line). Most of the system
> tests will be client side, and interface with the cluster through public
> APIs. We need a tool on top of MiniHBaseCluster or improve
> HBaseTestingUtility, so that tests can interface with the mini cluster or the
> actual cluster uniformly.
> 3. Port candidate unit tests to the integration tests module. Some of the
> candidates are:
> - TestAcidGuarantees / TestAtomicOperation
> - TestRegionBalancing (HBASE-6053)
> - TestFullLogReconstruction
> - TestMasterFailover
> - TestImportExport
> - TestMultiVersions / TestKeepDeletes
> - TestFromClientSide
> - TestShell and src/test/ruby
> - TestRollingRestart
> - Test**OnCluster
> - Balancer tests
> These tests should continue to be run as unit tests w/o any change in
> semantics. However, given an actual cluster, they should use that, instead of
> spinning a mini cluster.
> 4. Add more tests, especially, long running ingestion tests (goraci, BigTop's
> TestLoadAndVerify, LoadTestTool), and chaos monkey style fault tests.
> All suggestions welcome.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
