You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
object-is-loaded-matches
✗ returns false if the object shows any content
expected true to be false
AssertionError@node_modules/chai/chai.js:9227:13
[3]</module.exports/Assertion.prototype.assert@node_modules/chai/chai.js:253:13
[5]</module.exports/<@node_modules/chai/chai.js:1101:10
propertyGetter@node_modules/chai/chai.js:7985:29
proxyGetter@node_modules/chai/chai.js:9025:22
[6]</module.exports/assert.isFalse@node_modules/chai/chai.js:4638:5
@test/rule-matches/object-is-loaded-matches.js:37:12
Often passes on rerun
How to Reproduce
Wait for CI to fail
Additional context
n/a
The text was updated successfully, but these errors were encountered:
…re time to load <object> data (#4530)
These test failures are happening because the test isn't allowing
sufficient time for slower test scenarios (headed browsers in CI
machines) to finish setting up test fixtures before testing against
them.
I experimented with using `load`/`error` events on the fixtures instead
of a flat time, but this didn't work reliably; in the case where the
browser renders fallback content, it fires the `error` event *before*
the fallback content is ready, at least in Chromium stable. I wanted to
stick to a timebox for this so I settled for just increasing the time
allotment instead.
Closes: #4529
Product
axe-core
Product Version
4.9.1
Latest Version
Issue Description
Expectation
Test should work consistently
Actual
Test regularly fails (example) like this:
Often passes on rerun
How to Reproduce
Wait for CI to fail
Additional context
n/a
The text was updated successfully, but these errors were encountered: