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

Added CCS test for data view functionality. #124586

Merged
merged 23 commits into from
Feb 24, 2022

Conversation

cuff-links
Copy link
Contributor

Closes #124189

@cuff-links cuff-links marked this pull request as draft February 5, 2022 06:14
@cuff-links cuff-links added backport:skip This commit does not require backporting release_note:skip Skip the PR/issue when compiling release notes Feature:Functional Testing test_ui_functional labels Feb 5, 2022
@cuff-links cuff-links marked this pull request as ready for review February 9, 2022 06:11
@cuff-links cuff-links added v8.2.0 v7.17.0 auto-backport Deprecated: Automatically backport this PR after it's merged and removed backport:skip This commit does not require backporting labels Feb 9, 2022
@cuff-links
Copy link
Contributor Author

@LeeDr @spalger @stacey-gammon We got this first CCS test passing. @LeeDr and I were talking about next steps regarding whether we would migrate our current discover tests (and any tests that could also use CCS) to use CCS instead of local search. Would we consider local search sufficiently tested if a CCS test passes? Should we duplicate the tests? If so, which benefit most from using CCS in automation?

@stacey-gammon
Copy link
Contributor

Would we consider local search sufficiently tested if a CCS test passes?

I would, yes.

Should we duplicate the tests?

I wouldn't.

If so, which benefit most from using CCS in automation?

I would see if you could integrate CCS into the existing dashboard load tests. They cover a lot of searching, visualization types, embeddable, and filtering.

@cuff-links
Copy link
Contributor Author

@LeeDr I was looking into this test failure. Turns out this test that we added is skipped in CI. Just so happened. We should get that fixed anything. #124990

@cuff-links cuff-links merged commit 1e16db4 into elastic:main Feb 24, 2022
@kibanamachine
Copy link
Contributor

💔 All backports failed

Status Branch Result
7.17 Backport failed because of merge conflicts

How to fix

Re-run the backport manually:

node scripts/backport --pr 124586

Questions ?

Please refer to the Backport tool documentation

@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 124586 or prevent reminders by adding the backport:skip label.

1 similar comment
@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 124586 or prevent reminders by adding the backport:skip label.

lucasfcosta pushed a commit to lucasfcosta/kibana that referenced this pull request Mar 2, 2022
* Added CCS test for data view functionality.

* Changed how we are approaching the test. Just adding a remote to exercise the CCS functionality.

* Adjusted test to use correct port for remote cluster.

* Added and corrected config for the tests to be able to run.

* Changed test title.

* Added functional ccs suite to functional test runner script.

* Changed config.ts to config.js

* Moved es to before clause.

* Added await for an async call.

* Added await for an async call.

* Updated saved queries test to use CCS. One test is failing, all others are passing.

* Merge branch 'main' of github.com:elastic/kibana into CCS_Functional_Test_POC

* Fixed a reference.

* Removed the OSS tests since we created CCS versions of them.

* Removed tests from index file.

* Restored test files per comment with matthias.

* Did some cleanup of comments.

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 124586 or prevent reminders by adding the backport:skip label.

1 similar comment
@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 124586 or prevent reminders by adding the backport:skip label.

@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 124586 or prevent reminders by adding the backport:skip label.

cuff-links added a commit to cuff-links/kibana that referenced this pull request Mar 8, 2022
* Added CCS test for data view functionality.

* Changed how we are approaching the test. Just adding a remote to exercise the CCS functionality.

* Adjusted test to use correct port for remote cluster.

* Added and corrected config for the tests to be able to run.

* Changed test title.

* Added functional ccs suite to functional test runner script.

* Changed config.ts to config.js

* Moved es to before clause.

* Added await for an async call.

* Added await for an async call.

* Updated saved queries test to use CCS. One test is failing, all others are passing.

* Merge branch 'main' of github.com:elastic/kibana into CCS_Functional_Test_POC

* Fixed a reference.

* Removed the OSS tests since we created CCS versions of them.

* Removed tests from index file.

* Restored test files per comment with matthias.

* Did some cleanup of comments.

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit 1e16db4)
cuff-links added a commit to cuff-links/kibana that referenced this pull request Mar 8, 2022
* Added CCS test for data view functionality.

* Changed how we are approaching the test. Just adding a remote to exercise the CCS functionality.

* Adjusted test to use correct port for remote cluster.

* Added and corrected config for the tests to be able to run.

* Changed test title.

* Added functional ccs suite to functional test runner script.

* Changed config.ts to config.js

* Moved es to before clause.

* Added await for an async call.

* Added await for an async call.

* Updated saved queries test to use CCS. One test is failing, all others are passing.

* Merge branch 'main' of github.com:elastic/kibana into CCS_Functional_Test_POC

* Fixed a reference.

* Removed the OSS tests since we created CCS versions of them.

* Removed tests from index file.

* Restored test files per comment with matthias.

* Did some cleanup of comments.

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit 1e16db4)

# Conflicts:
#	scripts/functional_tests.js
@cuff-links cuff-links removed the v8.0.2 label Mar 8, 2022
@kibanamachine
Copy link
Contributor

Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync.

1 similar comment
@kibanamachine
Copy link
Contributor

Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync.

@stacey-gammon
Copy link
Contributor

@cuff-links can you either backport or add a backport-skip label? I'm getting these reminder emails every day. :)

@cuff-links
Copy link
Contributor Author

Will do. I will manually backport these once the PR that it depends on is backported.

@cuff-links cuff-links added the backport:skip This commit does not require backporting label Mar 10, 2022
@kibanamachine kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label Mar 10, 2022
@cuff-links cuff-links added backport missing Added to PRs automatically when the are determined to be missing a backport. and removed auto-backport Deprecated: Automatically backport this PR after it's merged labels Mar 10, 2022
@kibanamachine kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label Mar 10, 2022
cuff-links pushed a commit that referenced this pull request Mar 10, 2022
* Added CCS test for data view functionality. (#124586)

* Added CCS test for data view functionality.

* Changed how we are approaching the test. Just adding a remote to exercise the CCS functionality.

* Adjusted test to use correct port for remote cluster.

* Added and corrected config for the tests to be able to run.

* Changed test title.

* Added functional ccs suite to functional test runner script.

* Changed config.ts to config.js

* Moved es to before clause.

* Added await for an async call.

* Added await for an async call.

* Updated saved queries test to use CCS. One test is failing, all others are passing.

* Merge branch 'main' of github.com:elastic/kibana into CCS_Functional_Test_POC

* Fixed a reference.

* Removed the OSS tests since we created CCS versions of them.

* Removed tests from index file.

* Restored test files per comment with matthias.

* Did some cleanup of comments.

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit 1e16db4)

* Fixed the core-migration version on the date_nested_ccs.json

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting Feature:Functional Testing release_note:skip Skip the PR/issue when compiling release notes test_ui_functional v8.1.0 v8.2.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CCS POC functional test changes
6 participants