Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[UPTIME] Migrate settings e2e tests to a BDD approach #63252

Closed
mdelapenya opened this issue Apr 10, 2020 · 5 comments
Closed

[UPTIME] Migrate settings e2e tests to a BDD approach #63252

mdelapenya opened this issue Apr 10, 2020 · 5 comments
Assignees
Labels
Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability test_ui_functional

Comments

@mdelapenya
Copy link
Contributor

We want to rewrite this test https://github.com/elastic/kibana/blob/master/x-pack/test/functional/apps/uptime/settings.ts using BDD (Gherkin + Cucumber).

We decided not to start with Cypress for now, although it's in the plans.

@mdelapenya mdelapenya added test_ui_functional Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability labels Apr 10, 2020
@mdelapenya mdelapenya self-assigned this Apr 10, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/uptime (Team:uptime)

@mdelapenya
Copy link
Contributor Author

mdelapenya commented Apr 14, 2020

Running the tests

  1. Prepare the runtime dependencies: Kibana & Elasticsearch, from $KIBANA_ROOT/x-pack directory:
  2. Add FTR (Functional Test Runner) tags support (https://www.elastic.co/guide/en/kibana/current/development-functional-tests.html)
  3. In another terminal, from $KIBANA_ROOT/x-pack, run the tests of interest:
    • $ node scripts/functional_test_runner --include-tag=uptime-settings

Although the 3 tests pass, I can see this error:

         │ debg Find.findByCssSelector('[data-test-subj="heartbeat-indices-input-loaded"]') with timeout=5000
         │ERROR browser[SEVERE] http://localhost:5620/api/uptime/snapshot/count?dateRangeStart=now-15m&dateRangeEnd=now - Failed to load resource: the server responded with a status of 500 (Internal Server Error)
         │ERROR browser[SEVERE] http://localhost:5620/bundles/uptime.bundle.js 17129:20 Error: Internal Server Error
         │          at Fetch._callee3$ (http://localhost:5620/bundles/commons.bundle.js:12109:23)
         │          at tryCatch (http://localhost:5620/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:372675:40)
         │          at Generator.invoke [as _invoke] (http://localhost:5620/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:372901:22)
         │          at Generator.prototype.<computed> [as next] (http://localhost:5620/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:372727:21)
         │          at asyncGeneratorStep (http://localhost:5620/bundles/commons.bundle.js:11846:103)
         │          at _next (http://localhost:5620/bundles/commons.bundle.js:11848:194)

@elastic/uptime does this log error seems familiar to you?

@tylersmalley
Copy link
Contributor

In another terminal:

$ node scripts/functional_test

You actually want to use node scripts/functional_test_runner as this uses the server setup through the previous command.

@mdelapenya
Copy link
Contributor Author

We are going to put this on hold until we have BDD support in FTR. See #63892

@mdelapenya
Copy link
Contributor Author

I think this can be closed for now

@zube zube bot added [zube]: Done and removed [zube]: Ready labels Jul 28, 2022
@zube zube bot removed the [zube]: Done label Oct 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability test_ui_functional
Projects
None yet
Development

No branches or pull requests

3 participants