Test teardown sequencing issue with the setupEngine helper. about ember-engines HOT 2 OPEN

Thank you for the detailed explanation @brettburley!

Before reading last sentence, was thinking about using clearRender(), so appears we both think in the same direction.

from ember-engines.

Ha! I was considering introducing the clearRender() call to the setupRenderingTest helper in ember-qunit as an afterEach hook. However, it seems to trigger failures in many of our test suites that have blur handlers on inputs and end the test with a focused input... Chrome has a long-time bug where the blur event is incorrectly fired on DOM removal: https://issues.chromium.org/issues/41484175, and that triggers the tracked property assertion failure as reported in emberjs/ember.js#19010.

It seems like clearRender() removes the DOM before destroying the component instance. When the view is destroyed through the teardownContext destroy chain, destroy is invoked first on the component which removes the event handlers before the DOM is removed.

from ember-engines.