Failing test: X-Pack Endpoint Functional Tests on Serverless.x-pack/test/security_solution_endpoint/apps/endpoint/responder·ts - endpoint Response Actions Responder from timeline should show Responder from alert in a timeline

[kibanamachine]

A test failed on a tracked branch

Error: expected testSubject(superDatePickerQuickMenu) to exist
    at TestSubjects.existOrFail (test_subjects.ts:71:13)
    at Object.clickActionLogSuperDatePickerQuickMenuButton (endpoint_responder.ts:53:5)
    at performResponderSanityChecks (responder.ts:41:5)
    at Context.<anonymous> (responder.ts:204:9)
    at Object.apply (wrap_function.js:73:16)

First failure: CI Build - main

[elasticmachine]

Pinging @elastic/security-defend-workflows (Team:Defend Workflows)

[ashokaditya]

The cause of failure is due to a tour popup blocking the buttons below. We've already fixed this issue in /pull/172303. There's no reason that it should fail on #171760 give that it was merged after the fix PR. Unless, the CI ran before syncing with main which could cause in the test failure. I'm going to keep an eye on this one for a day before closing it.

[kibanamachine]

New failure: CI Build - main

[ashokaditya]

This is a new failure on serverless CI tests ☝🏼 Might be related to changes in /pull/172030. Looking into it!

[logeekal]

I have triggered a flaky test run because this test seems to be passing locally everytime

https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4211

[logeekal]

Hello @ashokaditya ,

I looked into the above flaky test runner and it looks like there was only one failure of a different test but with same reason.

Reason is that test clicks on below highlighted button but the popover never shows up and as you can see in below code. It could be for n number of reasons such as proper hydration or the button is not yet active.

We face this kind of error in cypress as well but we have way to repeatedly click a button until the required css selector shows up. Do you also employ this kind of technique in FTR somewhere as well?

kibana/x-pack/test/security_solution_endpoint/page_objects/endpoint_responder.ts

Lines 46 to 55 in 16f09fd

	const clickActionLogSuperDatePickerQuickMenuButton = async (): Promise<void> => {
	await testSubjects.findService.clickByCssSelector(
	`${testSubjSelector(TEST_SUBJ.actionLogFlyout)} ${testSubjSelector(
	'superDatePickerToggleQuickMenuButton'
	)}`
	);
	await testSubjects.existOrFail('superDatePickerQuickMenu');
	};

[ashokaditya]

@logeekal thanks for looking into this. I am not aware if we can do this on FTR. We could surely benefit with such a technique in the tests. Can you point me to a cypress test where you repeatedly click a button until the css selector shows up.

[ashokaditya]

related tickets

#170435
#172512

[ashokaditya]

/pull/175454

[logeekal]

@ashokaditya , Below is one such example. We run statements 206,207 till 209 is true.

kibana/x-pack/test/security_solution_cypress/cypress/tasks/alerts.ts

Lines 201 to 213 in 8287a0a

	export const clearAllSelections = (filterIndex: number) => {
	cy.get(CONTROL_GROUP).scrollIntoView();
	recurse(
	() => {
	cy.get(CONTROL_FRAME_TITLE).eq(filterIndex).realHover();
	return cy.get(OPTION_LIST_CLEAR_BTN).eq(filterIndex);
	},
	($el) => $el.is(':visible')
	);
	cy.get(OPTION_LIST_CLEAR_BTN).eq(filterIndex).should('be.visible').trigger('click');
	};

[ashokaditya]

We removed the FTR test in /pull/177740. Thetests were failing as there's a change in the timelines UI. We decided to cover it in cypress tests if not already covered.