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

Failing test: Firefox UI Functional Tests.test/functional/apps/discover/_field_data_with_fields_api·ts - discover app discover tab with new fields API field data shows top-level object keys #129844

Merged
merged 2 commits into from
Apr 13, 2022

Conversation

DianaDerevyankina
Copy link
Contributor

@DianaDerevyankina DianaDerevyankina commented Apr 8, 2022

Closes #127905

Summary

Added waitUntilLoadingHasFinished before expect checks and wrap them into retry.try.

image

image

For maintainers

…er/_field_data_with_fields_api·ts - discover app discover tab with new fields API field data shows top-level object keys
@DianaDerevyankina DianaDerevyankina self-assigned this Apr 8, 2022
@DianaDerevyankina DianaDerevyankina added release_note:skip Skip the PR/issue when compiling release notes auto-backport Deprecated - use backport:version if exact versions are needed Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. v8.2.0 v8.3.0 labels Apr 8, 2022
Copy link
Member

@kertal kertal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kertal kertal added the Feature:Discover Discover Application label Apr 11, 2022
@alexwizp alexwizp marked this pull request as ready for review April 12, 2022 07:12
@alexwizp alexwizp requested a review from a team as a code owner April 12, 2022 07:12
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)


const field = await PageObjects.discover.getDocTableIndex(1);
expect(field).to.contain('relatedContent.url');
const field = await PageObjects.discover.getDocTableIndex(1);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this change fixes the problem, but strategically, I still would like to not put try-retry in different places where we have a problem. Tests should be readable, and such logic is placed in PageObjects.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree we could improve it, but also I think it should not block from moving forward

@@ -92,12 +91,14 @@ export default function ({ getService, getPageObjects }: FtrProviderContext) {
hash.replace('columns:!()', 'columns:!(relatedContent)'),
{ useActualUrl: true }
);

await PageObjects.header.waitUntilLoadingHasFinished();
Copy link
Contributor

@alexwizp alexwizp Apr 12, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this mean that we need to add this to all places where navigation in Discover occurs?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It depends: if initially there's check of field list or the document table required, PageObjects.header.waitUntilLoadingHasFinished is recommended

Copy link
Contributor

@alexwizp alexwizp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved, but 2 questions were added

@kertal
Copy link
Member

kertal commented Apr 12, 2022

@elasticmachine merge upstream

Copy link
Member

@kertal kertal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thx for taking care of this 🙏


const field = await PageObjects.discover.getDocTableIndex(1);
expect(field).to.contain('relatedContent.url');
const field = await PageObjects.discover.getDocTableIndex(1);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree we could improve it, but also I think it should not block from moving forward

@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

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

cc @dziyanadzeraviankina

@DianaDerevyankina DianaDerevyankina merged commit f814e0f into elastic:main Apr 13, 2022
kibanamachine pushed a commit that referenced this pull request Apr 13, 2022
…er/_field_data_with_fields_api·ts - discover app discover tab with new fields API field data shows top-level object keys (#129844)

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

💚 All backports created successfully

Status Branch Result
8.2

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

kibanamachine added a commit that referenced this pull request Apr 13, 2022
…er/_field_data_with_fields_api·ts - discover app discover tab with new fields API field data shows top-level object keys (#129844) (#130104)

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

Co-authored-by: Diana Derevyankina <54894989+DziyanaDzeraviankina@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Deprecated - use backport:version if exact versions are needed Feature:Discover Discover Application release_note:skip Skip the PR/issue when compiling release notes Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. v8.2.0 v8.3.0
Projects
None yet
6 participants