[
https://issues.apache.org/jira/browse/METRON-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16280992#comment-16280992
]
ASF GitHub Bot commented on METRON-1344:
----------------------------------------
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/858
@justinleet latest commit includes the changes I had to make to switch a
preexisting integration test to the new infrastructure. I verified it works
locally, we'll see how it goes with Travis.
It was pretty straightforward and consisted of mainly 2 steps:
1. Remove the in memory components and replace any helper methods for
setup/teardown
2. Add a namespace to all the test assets (indices and doc types in this
case)
I believe converting other tests will follow this pattern as well. To
answer @ottobackwards's original question about
[#854](https://github.com/apache/metron/pull/854), adding namespaces will be
required when running the tests in parallel against shared infrastructure.
Cleaning up at the beginning/end won't be enough.
This is meant only as an example, happy to revert it and add it in a future
PR.
> Externalize the infrastructural components using integration tests
> ------------------------------------------------------------------
>
> Key: METRON-1344
> URL: https://issues.apache.org/jira/browse/METRON-1344
> Project: Metron
> Issue Type: Improvement
> Reporter: Ryan Merriman
> Assignee: Ryan Merriman
>
> As we move towards adding the Alerts UI e2e test to our continuous build, we
> need to remove the dependence on vagrant full dev and provide equivalent
> infrastructure within Travis. This will include all the services that the
> e2e tests depend on including Kafka, Zookeeper, Elasticsearch (possibly
> HBase), and Metron REST.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
