2796e7798b
* Stabilize tests involving absolute timepicker The asynchronous nature of angular's digest cycle and the page rendering in the browser can lead to situations in which `isGlobalLoadingIndicatorHidden()` returns true because the loading triggered by the previous action has not yet started. In this case subsequent actions incorrectly assume the loading has already been completed. This is probably responsible for the flakiness described in #10302. The newly introduced `waitUntilLoadingHasFinished` first waits for a duration up to `defaultTimeout` for the loading indicator to appear before waiting for it to be hidden again. In the best case this will reduce the false positive rate of `setAbsoluteTimerange()`. In the worst case the function will wait `defaultTimeout` longer than when just using `isGlobalLoadingIndicatorHidden`. fixes #10302 |
||
|---|---|---|
| .. | ||
| dev_certs | ||
| fixtures | ||
| functional | ||
| screenshots/baseline | ||
| scripts | ||
| support | ||
| unit/api | ||
| utils | ||
| visual_regression | ||
| intern.js | ||
| intern_api.js | ||
| intern_visual_regression.js | ||
| mocha.opts | ||
| mocha_setup.js | ||
| server_config.js | ||
| shield.js | ||