-
Notifications
You must be signed in to change notification settings - Fork 174
Hook up integration test for Alerting Kibana plugin #600
Comments
Hi @tlfeng, I am working on this issue. However while doing so looks like the the non security tests are working well but for security test it is failing. I am testing with Please let us know if you have any update to resolve it. Till then I'll work on adding non-security tests. |
Thank you for informing me the result of the workflow runs. Let me take a loot at the failures. |
Sure @tlfeng . Let me know when you fix it or have an update. |
@tlfeng , Any update on this issue? |
Hi @bbarani, sorry that I haven't took much time on finding the solution. I will try to find the fix in this week, including checking how other plugins deal with it. |
Hi @gaiksaya, |
Hi @tlfeng , Thank you for fixing it. I have created the PR to add the tests in our workflows. |
Thank you for your rapid action! 👍👍 @gaiksaya |
Request adding integration test for Alerting Kibana plugin to the build workflow with and without security
Assumption:
With security: Elasticsearch is running at http://localhost:9200, Kibana is running at http://localhost:5601
Without security: Elasticsearch is running at https://localhost:9200, Kibana is running at http://localhost:5601
Step to run the test:
kibana/plugins/alerting-kibana-plugin
), run command in below to start the Cypress testWith security:
yarn run cypress run --env security_enabled=true
WIthout security:
yarn run cypress run
A successful workflow run in Alerting Kibana plugin repo, without security enabled:
https://github.com/opendistro-for-elasticsearch/alerting-kibana-plugin/actions/runs/489045146
(A test failure is expected when running against Alerting Kibana plugin v1.12.0.2)
The PR to support running Cypress test in ODFE cluster with security enabled for Alerting Kibana plugin:
opendistro-for-elasticsearch/alerting-kibana-plugin#235
The text was updated successfully, but these errors were encountered: