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
Occasionally when I run npm run test locally, Karma will throw an error saying Some of your tests did a full page reload! and abort the test run. I think there's a bug in one of our tests that only occurs depending on the order in which they run (which is intentionally randomised). I can't see any tests that call window.location.reload(), so it must be triggered by some other means (maybe a click or form submission). This is a fun doozy.
Steps to reproduce
Run npm run test multiple times until the error occurs.
Expected result
The test run should always finish.
Actual result
The test run sometimes gets aborted early with the above error.
Environment
Firefox & Chrome, macOS
The text was updated successfully, but these errors were encountered:
May be it is not a bedrock's bug. It can be a karma bug. btw This was an issue before version 6.0.0. See this. @alexgibson are you still getting this error?
Description
Occasionally when I run
npm run test
locally, Karma will throw an error sayingSome of your tests did a full page reload!
and abort the test run. I think there's a bug in one of our tests that only occurs depending on the order in which they run (which is intentionally randomised). I can't see any tests that callwindow.location.reload()
, so it must be triggered by some other means (maybe a click or form submission). This is a fun doozy.Steps to reproduce
Run
npm run test
multiple times until the error occurs.Expected result
The test run should always finish.
Actual result
The test run sometimes gets aborted early with the above error.
Environment
Firefox & Chrome, macOS
The text was updated successfully, but these errors were encountered: