github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-24 17:59:23 -04:00
Code Issues Projects Releases Packages Wiki Activity

[SecuritySolution] Delete startedAt check from init_and_status_apis FTR test (#212074)

Browse source 
## Summary

Delete `startedAt` check from init_and_status_apis FTR test.
After @hop-dev [fixed](https://github.com/elastic/kibana/pull/211867)
the status flakiness by accepting `running` as a valid status, the
`startedAt` property has become optional. Deleting it should fix the
[flakiness](https://buildkite.com/elastic/kibana-on-merge/builds/62432#0195243b-92c2-4838-85c1-f06096a62e61).


### How to test it?
That is hard. The flakiness is very flaky ❄️ 
To test it locally, I added `waitFor status === 'running'` before the
`expect`
This commit is contained in:
Pablo Machado 2025-02-24 12:10:06 +01:00 • committed by GitHub
parent 6a7c904f92
commit 9fa4e56d19
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 0 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
x-pack/test/security_solution_api_integration/test_suites/entity_analytics/risk_engine/trial_license_complete_tier/init_and_status_apis.ts
View file

@ -763,7 +763,6 @@ export default ({ getService }: FtrProviderContext) => {
expect(status2.body.risk_engine_task_status?.runAt).to.be.a('string');
expectTaskIsHealthy(status2.body.risk_engine_task_status?.status);
expect(status2.body.risk_engine_task_status?.startedAt).to.be(undefined);
await riskEngineRoutes.disable();
const status3 = await riskEngineRoutes.getStatus();
@ -779,7 +778,6 @@ export default ({ getService }: FtrProviderContext) => {
expect(status4.body.risk_engine_task_status?.runAt).to.be.a('string');
expectTaskIsHealthy(status4.body.risk_engine_task_status?.status);
expect(status4.body.risk_engine_task_status?.startedAt).to.be(undefined);
});
});
});