Add autodiscover 2e2 testcases for Agent (standalone)#1645
Add autodiscover 2e2 testcases for Agent (standalone)#1645mdelapenya merged 13 commits intoelastic:masterfrom
Conversation
Signed-off-by: ChrsMark <chrismarkou92@gmail.com>
|
This pull request is now in conflict. Could you fix it @ChrsMark? 🙏 |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
Signed-off-by: ChrsMark <chrismarkou92@gmail.com>
Signed-off-by: ChrsMark <chrismarkou92@gmail.com>
| @@ -0,0 +1,9 @@ | |||
| @kubernetes-autodiscover | |||
| @elastic-agent | |||
| Feature: elastic-agent standalone | |||
|
@ChrsMark thanks for your first contribution to the project! It is indeed great! I'm only missing one change to add the new scenarios. As explained in the docs (https://github.com/elastic/e2e-testing/tree/master/e2e#feature-files-and-the-ci) the CI will use the - suite: "kubernetes-autodiscover"
platforms:
- labels: "ubuntu-18.04"
scenarios:
- name: "kubernetes autodiscover with elastic-agent"
tags: "kubernetes-autodiscover && elastic-agent"
- name: "kubernetes autodiscover with filebeat"
tags: "kubernetes-autodiscover && filebeat"
- name: "kubernetes autodiscover with heartbeat"
tags: "kubernetes-autodiscover && heartbeat"
- name: "kubernetes autodiscover with metricbeat"
tags: "kubernetes-autodiscover && metricbeat" |
mdelapenya
left a comment
There was a problem hiding this comment.
Only missing what described in #1645 (comment).
Once there, I'd merge this one :)
|
One last question: could you please add labels for backports?
|
Signed-off-by: ChrsMark <chrismarkou92@gmail.com>
Signed-off-by: ChrsMark <chrismarkou92@gmail.com>
Signed-off-by: ChrsMark <chrismarkou92@gmail.com>
|
I wonder what makes it failing on the CI while it works locally 🤔 |
e2e/_suites/kubernetes-autodiscover/features/elastic-agent.feature
Outdated
Show resolved
Hide resolved
e2e/_suites/kubernetes-autodiscover/testdata/templates/elastic-agent.yml.tmpl
Outdated
Show resolved
Hide resolved
I'm manually running the CI using TRACE log level: https://beats-ci.elastic.co/job/e2e-tests/job/e2e-testing-mbp/job/PR-1645/7/. Let's check if that error is repeatable |
|
@ChrsMark it passed, although the single failure that is currently present (windows related) is considered flaky. I'd say this is LGTM |
…ture Co-authored-by: Manuel de la Peña <social.mdelapenya@gmail.com>
…-agent.yml.tmpl Co-authored-by: Manuel de la Peña <social.mdelapenya@gmail.com>
|
Thanks for reviewing @mdelapenya ! After applying your suggestions the k8s suite failed again and I'm not sure I can understand the reason. I'm particularly concerned of introducing some flakiness here so could you spot where it fails when this happen? |
Signed-off-by: ChrsMark <chrismarkou92@gmail.com>
|
@ChrsMark this is ready to go, merging! |
* Add initial case Signed-off-by: ChrsMark <chrismarkou92@gmail.com> * Add go dep Signed-off-by: ChrsMark <chrismarkou92@gmail.com> * Add go dep Signed-off-by: ChrsMark <chrismarkou92@gmail.com> * Review changes and more tests Signed-off-by: ChrsMark <chrismarkou92@gmail.com> * Add more cases Signed-off-by: ChrsMark <chrismarkou92@gmail.com> * Add extra case Signed-off-by: ChrsMark <chrismarkou92@gmail.com> * Update e2e/_suites/kubernetes-autodiscover/features/elastic-agent.feature Co-authored-by: Manuel de la Peña <social.mdelapenya@gmail.com> * Update e2e/_suites/kubernetes-autodiscover/testdata/templates/elastic-agent.yml.tmpl Co-authored-by: Manuel de la Peña <social.mdelapenya@gmail.com> * Fix scope of cronjob test Signed-off-by: ChrsMark <chrismarkou92@gmail.com> * chore: fix go fmt * chore: do not destroy kind cluster in DEV mode Co-authored-by: Manuel de la Peña <social.mdelapenya@gmail.com> Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com> (cherry picked from commit a23b3b4)
|
❤️ thanks! |


What does this PR do?
This PR adds autodiscover test cases for elastic-agent standalone.
Why is it important?
To cover autodiscover in Agent with 2e2 tests.
Checklist
make unit-test), and they are passing locallymake noticein the proper directory)Related issues