Promise rejection tests give console.error logs, which causes
tests to fail
Some background: tests in IE11 started failing in #63. Probably a package update from the cache being invalidated. Some guesses:
Previously, the console.error was not being called until the test completed
The trackConsoleError was added (probably not, since this was added in 2018)
console.error is being called on Chrome when testing locally, so my guess is 1. I suppose we always had this race condition here. Maybe the way the promise polyfill queues promise rejections changed?
I could either do a deep dive into this, or set trackConsoleError to false, or stub it.
Some background: tests in IE11 started failing in #63. Probably a package update from the cache being invalidated. Some guesses:
console.error is being called on Chrome when testing locally, so my guess is 1. I suppose we always had this race condition here. Maybe the way the promise polyfill queues promise rejections changed?
I could either do a deep dive into this, or set trackConsoleError to false, or stub it.