[Search] Replace flaky FTR tests with Scout tests for Search Homepage#248381
[Search] Replace flaky FTR tests with Scout tests for Search Homepage#248381saikatsarkar056 merged 28 commits intoelastic:mainfrom
Conversation
- Create search_homepage.spec.ts with tests migrated from FTR - Add embedded console methods to homepage page object - Use uiSettings to disable V2 flag for testing V1 homepage - Tests: embedded dev console, page load verification
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#10390[❌] x-pack/solutions/search/plugins/search_homepage/test/scout/ui/parallel.playwright.config.ts: 0/200 tests passed. |
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#10391[❌] x-pack/solutions/search/plugins/search_homepage/test/scout/ui/parallel.playwright.config.ts: 0/200 tests passed. |
|
Flaky test runner was failing due to an invalid CLI flag. This PR fixes the issue. |
|
@elasticmachine merge upstream |
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#10408[✅] x-pack/solutions/search/plugins/search_homepage/test/scout/ui/parallel.playwright.config.ts: 15/15 tests passed. |
|
@elasticmachine merge upstream |
|
There are no new commits on the base branch. |
|
|
||
| test.describe('Search Homepage (V1)', { tag: ['@ess', '@svlSearch'] }, () => { | ||
| // Disable the V2 homepage to test the old (V1) homepage | ||
| test.beforeAll(async ({ kbnClient, esClient }) => { |
There was a problem hiding this comment.
Hey @saikatsarkar056
We are not going to re-enable v1 homepage. I think the ticket was not ready 100% 😬 But what we should do is instead, take a look at the flows from skipped homepage tests and implement similar ones on the new homepage where it makes sense.
There was a problem hiding this comment.
@efegurkan You are right. Let me modify this PR to cover only relevant changes needed for new homepage.
…a into scout_for_homepage
|
@efegurkan Could you please review the PR for another round? Thank you. |
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#10432[✅] x-pack/solutions/search/plugins/search_homepage/test/scout/ui/parallel.playwright.config.ts: 15/15 tests passed. |
|
@elasticmachine merge upstream |
…a into scout_for_homepage
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#10452[✅] x-pack/solutions/search/plugins/search_homepage/test/scout/ui/parallel.playwright.config.ts: 15/15 tests passed. |
|
/ci |
Pull Request is not mergeable
|
@elasticmachine merge upstream |
|
expected head sha didn’t match current head ref. |
|
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]
History
|
Summary
This PR migrates the FTR (Functional Test Runner) tests for the Search Homepage to Scout tests.
Background
The existing FTR tests for Search Homepage have been experiencing flakiness issues (see #226572), with several tests being skipped. This migration to Scout provides a more stable and maintainable test infrastructure.
How to Run Search Homepage Scout Tests
Prerequisites
Start the appropriate server first:
For Stateful (ESS)
node scripts/scout.js start-server --statefulFor Serverless
node scripts/scout.js start-server --serverless=esRun all Search Homepage tests with browser visible
npx playwright test --config x-pack/solutions/search/plugins/search_homepage/test/scout/ui/parallel.playwright.config.ts --project local --headed --grep "Search Homepage"Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesbackport:*labels.Identify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.