[
https://issues.apache.org/jira/browse/METRON-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16281002#comment-16281002
]
ASF GitHub Bot commented on METRON-1344:
----------------------------------------
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/858
@ottobackwards I also added a way to run the e2e tests locally. Once your
Docker app is up and running locally, get the $DOCKER_HOST ip address and
replace "localhost" with that ip address in
`metron-interface/metron-alerts/protractor.conf.js` (should be 3 places you
have to update). Mine looks something like this:
```
exports.config = {
...
baseUrl: 'http://192.168.99.100:4201/',
...
params: {
rest: {
url: '192.168.99.100:8082'
},
elasticsearch: {
url: '192.168.99.100:9210'
}
}
}
```
Then you can run the e2e tests with `cd metron-interface/metron-alerts &&
npm run e2e`
> 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)
