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
We have some tests in QUnit and some in jest. When the whole suite runs, jest invokes QUnit. It would be better to factor out the remaining use of QUnit and have one thing.
It's fine. Mostly it was a good choice here because it replaced a perl & bash based parallel runner for our various test suites. I don't think it's necessarily better than QUnit at the level of authoring individual tests.
@stefanpenner: related to test ergonomics, I think I'm still seeing babel/broccoli-babel-transpiler#169 in the embroider test suite. It manifests as a timeout when the jest-invoked QUnit process fails to exit, even though QUnit got to the end of its suite.
We have some tests in QUnit and some in jest. When the whole suite runs, jest invokes QUnit. It would be better to factor out the remaining use of QUnit and have one thing.
cc @Turbo87
The text was updated successfully, but these errors were encountered: