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

Functional test for saved objects import/export UI #44320

Closed
1 of 3 tasks
bhavyarm opened this issue Aug 28, 2019 · 2 comments
Closed
1 of 3 tasks

Functional test for saved objects import/export UI #44320

bhavyarm opened this issue Aug 28, 2019 · 2 comments

Comments

@bhavyarm
Copy link
Contributor

bhavyarm commented Aug 28, 2019

Tests for testing export/import using saved objects UI:

For 7.x to 8.x import:

Data set:
sample dashboards and all the beats dashboards viz .ndjson

Tests:

  1. To empty Kibana - import the file with related objects and make sure import works fine.
  2. To empty Kibana - import the file without related objects and make sure import works fine.
  3. Load esarchive with one index pattern - import a file with just one saved object and ensure Kibana lets us associate the saved object with the index pattern which we loaded and verify its accuracy.
  4. Export a dashboard with related objects - change the id of a saved object inside the dashboard - import it back -ensure Kibana behaves accurately

Technical challenges to work through:

  • Can import beats dashboards without enabling migration: true in beats.xml
  • Need to figure out a place to store saved objects json file
  • understand related objects
@bhavyarm
Copy link
Contributor Author

CC @LeeDr @dmlemeshko

@bhavyarm bhavyarm changed the title Functional test for saved objects UI Functional test for saved objects import/export UI Aug 28, 2019
@bhavyarm
Copy link
Contributor Author

I worked on this and the PR has been merged for a while now - #100828

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant