[
https://issues.apache.org/jira/browse/METRON-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16281751#comment-16281751
]
ASF GitHub Bot commented on METRON-1344:
----------------------------------------
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/858
I was more thinking about having to have a "Debugging Integration Tests"
readme.
I think having the in-memory stuff available is worth getting some feedback.
I have in the past debugged through the kafka topic and storm stuff when
looking to track down error messages and issues in the integration tests. I
don't know if that is something that happens often enough to warrant keeping
the in-memory stuff.
But, if we don't keep them, then would we want the docker testing
containers to be setup for debugging? Would it work? So the start.sh starts
with the debugging on, known ports etc.
> 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)
