343ce0ff31
We've seen a number of flaky test failures where the tests are waiting for the rendering count to be `11` but it is `12` for some reason (which is probably totally fine). This is causing tests to regularly fail when they probably shouldn't, so I've updated the `PageObjects.visualize.waitForRenderingCount()` to accept a `minimumCount` instead of an exact count that is expected. I've also updated the function to use `retry.waitFor()` for slightly better logging. ``` [00:01:13] │ debg Waiting up to 20000ms for rendering count to be greater than or equal to [3]... [00:01:13] │ debg TestSubjects.find(visualizationLoader) [00:01:13] │ debg findByCssSelector [data-test-subj~="visualizationLoader"] [00:01:13] │ debg -- currentRenderingCount=2 [00:01:13] │ debg TestSubjects.find(visualizationLoader) [00:01:13] │ debg findByCssSelector [data-test-subj~="visualizationLoader"] [00:01:13] │ debg -- currentRenderingCount=3 ``` |
||
|---|---|---|
| .. | ||
| api_integration | ||
| common | ||
| dev_certs | ||
| functional | ||
| plugin_functional | ||
| scripts | ||
| server_integration | ||