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
Currently, adding any tests that use the setupTest/setupRenderingTest/setupApplicationTest testing infrastructure causes those tests to "randomly" fail (due to timeout errors).
After digging into it a bit, the issue seems to be caused by using setApplication in tests/helpers/setup-destroy-ei-app.js. Calling setApplication there (and then running app.destroy) causes all subsequent @ember/test-helpers based tests to timeout (the application instance that you pass to setApplication is supposed to never be destroyed).
Currently, adding any tests that use the
setupTest
/setupRenderingTest
/setupApplicationTest
testing infrastructure causes those tests to "randomly" fail (due to timeout errors).After digging into it a bit, the issue seems to be caused by using
setApplication
intests/helpers/setup-destroy-ei-app.js
. CallingsetApplication
there (and then runningapp.destroy
) causes all subsequent@ember/test-helpers
based tests to timeout (the application instance that you pass tosetApplication
is supposed to never be destroyed).TODO:
ember-debug/main
eagerly does not cause knock on test failures (Ensure renderDebug is properly unregistered. #1202)setApplication
call insetup-destroy-ei-app.js
is reversed (Reset internal test helper state for EmberDebug tests. #1203)tests/helpers/setup-destroy-ei-app.js
to use a newersetupInspectorTest(hooks)
style API (IntroducesetupEmberDebugTest
test helper. #1204)The text was updated successfully, but these errors were encountered: