Code coverage: run more configs with functional tests

[dmlemeshko]

Summary

This PR extends set of functional tests configs that we execute to collect code coverage:

• Endpoint tests
• Tests with ES SSL
• Security tests with Basic license

Note: I think I didn't miss any other config with functional tests (running in Chrome browser), but if you think I did - please let me know.

Code coverage report is available here

Before:

After:

Endpoint plugin sources are listed in the report now

[jonathan-buttner]

Thanks @dmlemeshko ! Could you also add this one:

require.resolve('../test/plugin_functional/config.ts')

That has some tests for our Resolver embeddable used in the endpoint app.

cc: @oatkiller

[legrego]

Out of curiosity, how do we choose which test suites should be included for code coverage? I know we have the skipCoverage tag, but what determines why we tag a suite for exclusion?

[jonathan-buttner]

Thanks!

[dmlemeshko]

Out of curiosity, how do we choose which test suites should be included for code coverage? I know we have the skipCoverage tag, but what determines why we tag a suite for exclusion?

@legrego "Functional" code coverage is expected to run all the Kibana client-side tests, that can be executed in Chrome.
skipCoverage tag was added only to skip flaky/failing tests (yes, some tests fail only with source-mapped Kibana), just to have successful builds. I'm currently investigating failures and will create the issues.
The plan is not have it set anywhere :)

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: cb8188c

History

• 💛 Build #41186 was flaky 93afb8c

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[rylnd]

@dmlemeshko did you want to backport this to 7.x? I'm backporting #63430 and have conflicts with jenkins_xpack.sh. Not a problem either way, just want to make sure I'm resolving correctly.