-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Navigating to apps when welcome screen is present #39689
Comments
Pinging @elastic/kibana-operations |
Pinging @elastic/kibana-test-triage |
Is it possible to add |
Currently there is not -- I have a case open on that end too -- but after speaking with Spencer we thought it would be good to also have this, I will follow up. |
@liza-mae any update on the welcome screen? |
@jinmu03 I think I have a solution, it is currently in testing :) I will assign this issue to me. |
Fixed via elastic/elastic-stack-testing#390 |
Reopening for another test need, @pheyos is going to look at adding this functionality to FTR. |
The fix I put in only works on staging, but Robert wants to run these tests on production, I think bypassing the welcome screen will at least allow those tests to run and I agree there is value in running these tests on production too. One staging/production difference I found in #51522 and also possibly #55632 . |
The home app will show the welcome screen when there are no registered index patterns and the local storage key by adding await browser.setLocalStorageItem('home:welcome:show', 'false'); after line 32 in https://github.com/elastic/kibana/blob/7.6/x-pack/test/functional/page_objects/security_page.js#L32. This will make sure it is set after Kibana is loaded but before the welcome screen is already visible. @liza-mae What do you think? Would this be a good solution to you? |
@flash1293 nice! Yes this sounds like a good solution to me, let's give it a try. |
We have some cloud tests that are failing due to the welcome screen about 27 tests, although this setting is disabled in on-prem testing we don't have this option in cloud. It would be nice if our navigating methods in FTR could check for it and click to continue.
The text was updated successfully, but these errors were encountered: