Skip to content

[8.18] [Security Solution] Wait for Fleet setup completion in Cypress before running tests (#230632) #230883

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.

Sign up for GitHub

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

Merged
kibanamachine merged 1 commit into from
Aug 7, 2025
Merged

[8.18] [Security Solution] Wait for Fleet setup completion in Cypress before running tests (#230632) #230883

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions x-pack/test/security_solution_cypress/config.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,18 @@ export default async function ({ readConfigFile }: FtrConfigProviderContext) {
'--csp.strict=false',
'--csp.warnLegacyBrowsers=false',
],
runOptions: {
wait: FLEET_PLUGIN_READY_LOG_MESSAGE_REGEXP,
},
},
};
}

/**
* A log message indicating that Fleet plugin has completed any necessary setup logic
* to make sure test suites can run without race conditions with Fleet plugin initialization.
*
* The message must not be filtered out by the logging configuration. Subsequently higher log level is better.
* "Fleet setup completed" has the same "info" level as "Kibana server is ready" log message.
*/
const FLEET_PLUGIN_READY_LOG_MESSAGE_REGEXP = /Fleet setup completed/;
12 changes: 12 additions & 0 deletions x-pack/test/security_solution_cypress/serverless_config.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,19 @@ export default async function ({ readConfigFile }: FtrConfigProviderContext) {
'--csp.strict=false',
'--csp.warnLegacyBrowsers=false',
],
runOptions: {
wait: FLEET_PLUGIN_READY_LOG_MESSAGE_REGEXP,
},
},
testRunner: SecuritySolutionConfigurableCypressTestRunner,
};
}

/**
* A log message indicating that Fleet plugin has completed any necessary setup logic
* to make sure test suites can run without race conditions with Fleet plugin initialization.
*
* The message must not be filtered out by the logging configuration. Subsequently higher log level is better.
* "Fleet setup completed" has the same "info" level as "Kibana server is ready" log message.
*/
const FLEET_PLUGIN_READY_LOG_MESSAGE_REGEXP = /Fleet setup completed/;