Using @elastic/synthetics to run uptime e2e tests

[shahzad31]

Summary

Using https://github.com/elastic/synthetics to run uptime kibana functional tests

This contains a simple journey which runs against live heartbeat data using docker

To Start test server:

This is using standard kibana ftr server, in exception that it doesn't start esCluster and instead uses docker to start heartbeat and elasticsearch. Since it would be a hassle communicating from heartbeat docker to outside escluster.

in uptime dir

do

node scripts/start_e2e_server.js

This will start kibana

to run a test once server is up

node scripts/start_e2e_runner.js

runner will run test and output results:

[vigneshshanmugam]

Nice work.

Should we use synthetics docker image or use npm packages like in this example

I would stay with just using the library from the NPM instead of going through heartbeat as we want it to behave a test runner rather than for monitoring purposes (Uptime UI on top of the existing CLI).

Which version of synthetics to use? Clone synthetics repo to always use latest master?

Use the latest published one from NPM, using master from synthetics would be a wrong choice as we might break at some point and that means the PR's in kibana would be blocked. Also it aligns more with how our users would be using the tool instead of staying latest on master.

Hope this helps.

[shahzad31]

@elasticmachine merge upstream

[v1v]

This is the new section after restructuring the CI pipeline to support two parallel stages, one for the existing e2e for the APM-UI and a new stage (this one) for the Uptime e2e.

[v1v]

There is now a new check for the e2e for uptime-ui:

The CI changes are half implemented now, I'll work then in the implementation details regarding running the uptime e2e in the CI.

[shahzad31]

@elasticmachine merge upstream

[shahzad31]

@v1v looking awesome

[v1v]

Once L159 produces the junit files, then you can add something like

Suggested change

	archiveArtifacts(allowEmptyArchive: true, artifacts: 'uptime-e2e-docker.log')
	archiveArtifacts(allowEmptyArchive: true, artifacts: 'uptime-e2e-docker.log')
	junit(allowEmptyResults: true, testResults: '<RELATIVE_PATH_FROM_UPTIME_E2E_DIR>/<FILE_NAME>.xml')

But please replace '<RELATIVE_PATH_FROM_UPTIME_E2E_DIR>/<FILE_NAME>.xml'

[kibanamachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request
• Commit: 92f3b41
• Storybooks not built
• Pipeline Steps (look for red circles / failed steps)
• Interpreting CI Failures

Failed CI Steps

• Setup Build Environment and Dependencies
• Setup Build Environment and Dependencies
• Setup Build Environment and Dependencies
• Setup Build Environment and Dependencies
• Error signal

Metrics [docs]

‼️ ERROR: metrics for 92f3b41 were not reported

History

• 💔 Build #136931 failed c032b11
• 💔 Build #122324 failed fa65022
• 💔 Build #122288 failed ce0d72e
• 💔 Build #119096 failed 0befc3d

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

cc @shahzad31