apm-server tests

[jalvz]

What does this PR do?

Test the apm server setup used on Cloud

Why is it important?

Because it's Cloud

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have run the Unit tests for the CLI, and they are passing locally
• I have run the End-2-End tests for the suite I'm working on, and they are passing locally
• I have noticed new Go dependencies (run make notice in the proper directory)

Related issues

Closes #890

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Build Cause: Pull request #1083 updated

• Start Time: 2021-04-28T11:57:51.589+0000

• Duration: 21 min 38 sec

• Commit: d40400a

Test stats 🧪

Test	Results
Failed	0
Passed	152
Skipped	0
Total	152

Trends 🧪

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test	Results
Failed	0
Passed	152
Skipped	0
Total	152

[mergify]

This pull request is now in conflict. Could you fix it @jalvz? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b apm-on-cloud-test upstream/apm-on-cloud-test
git merge upstream/master
git push upstream apm-on-cloud-test

[jalvz]

@mdelapenya can you help me understand test failures? there are all in a different suite (metricbeat) and look like this: No such file or directory: <home>/.op/compose/services/dropwizard/docker-compose.yml

Replace "dropwizard" which every service (redis, etc). I can reproduce the error locally, but I can also reproduce it in master (with SUITE="metricbeat" TAGS="dropwizard" LOG_LEVEL=TRACE DEVELOPER_MODE=true make -C e2e functional-test so I don't know how to go from there.)

[mdelapenya]

@mdelapenya can you help me understand test failures? there are all in a different suite (metricbeat) and look like this: No such file or directory: <home>/.op/compose/services/dropwizard/docker-compose.yml

Replace "dropwizard" which every service (redis, etc). I can reproduce the error locally, but I can also reproduce it in master (with SUITE="metricbeat" TAGS="dropwizard" LOG_LEVEL=TRACE DEVELOPER_MODE=true make -C e2e functional-test so I don't know how to go from there.)

Sorry for the back-and-forth with this. Because we use same integrations as in Beats repository, we must sync them for first time from that repo. We have make -C cli sync-integrations to do so. Once fetched, you should never need to do that, unless the files are not there.

I know this should be more transparent from development stand point, it's something we are thinking about to change, but we did not want to block the user cloning a big repo such as Beats with certain frequency. Of course, this can be changed from improvement.

[mdelapenya]

I thought it was documented for the metricbeat test suite, but it's for Fleet, which is incorrect. We will change it in a new issue

[jalvz]

Thanks. I think tests should depend on the state on my machine as least as possible, and should be as self contained as possible (make test should work or fail on its own, not depending on which other commands did or did not run before it).

I'll open an issue for that.