[
https://issues.apache.org/jira/browse/BIGTOP-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180951#comment-14180951
]
jay vyas edited comment on BIGTOP-1493 at 10/23/14 2:56 AM:
------------------------------------------------------------
thanks, [~cos] , your opinion is intrinsically important, and id like to
convince you ....
- bigtop is known as an integration testing provider : users can trust that our
tests are platform neutral and curated by bigdata experts from a variety of
fields.
- Users need *to test their cluster, even though they arent using a pure bigtop
based deployment* and the scenarios for testing *might exceed those covered
bybigtop packaging* .
So, given the above premises - Id like to propose that we allow ( on a *case by
case* basis) adding of tests for components of the big data ecosystem which are
*synergistic to bigtop's stack*.
Is that a good policy ? Or *do you think that bigtop's tests should be limited
to components which bigtop is packaging* ? welcome others to chime in as well
!
was (Author: jayunit100):
thanks, [~cos] , your opinion is intrinsically important, and id like to
convince you ....
- bigtop is known as an integration testing provider : users can trust that our
tests are platform neutral and curated by bigdata experts from a variety of
fields.
- Users need * to test their cluster, even though they arent using a pure
bigtop based distribution.* and the scenarios for testing might exceed bigtop
packaging .
So, given the above premises - Id like to propose that we allow ( on a *case by
case* basis) adding of tests for components of the big data ecosystem which are
synergistic to bigtop's stack.
Is that a good policy ? Or do you think that bigtop's tests should be limited
to components which bigtop is packaging ? welcome others to chime in as well
> Add smoke test for tachyon
> --------------------------
>
> Key: BIGTOP-1493
> URL: https://issues.apache.org/jira/browse/BIGTOP-1493
> Project: Bigtop
> Issue Type: Test
> Components: tests
> Reporter: jay vyas
>
> Tachyon as an in memory cache will be emerging as a common feature in hadoop
> and spark based clusters.
> Lets create a smoke test under the {{smoke-tests}} which uses the
> {{tachyon:///}} url.
> To get started with the smoke tests, you can
> 1) Run the vagrant recipe under bigtop-deploy/vm/vagrant-puppet . This will
> demonstrate the way you spin up a bigtop based hadoop cluster.
> 2) Now, you can do {{vagrant ssh}} into your cluster, and simply edit the
> smoke tests or install stuff. Re running the smoke-tests.sh file should test
> that your new tests work . At that point, just exit your VM, and commit your
> changes and submit the new patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
