Tobias Bieniek

```js import { expect } from 'chai'; import { describe, it, beforeEach } from 'mocha'; import { setupComponentTest } from 'ember-mocha'; describe('Unit | Component | foo bar', function() { setupComponentTest('foo-bar',...

that link goes to 404 for me 🤔 IMHO similar to how QUnit does it we should not start any runloops automatically in Mocha. This has been a major pain...

@a13o did you test these changes with a few projects? e.g. https://github.com/TryGhost/Ghost-Admin is a good open source project to test against

that's good to hear, thanks @apellerano-pw!

> has the possibility of a major version bump and breaking change been discussed? If so I would rather yield to that than continue this approach of removing official mocha...

see https://github.com/ember-cli/ember-cli-mocha/issues/167

@apellerano-pw don't get me wrong, I would love to update. but last time I tried I couldn't find a way to support the "old testing APIs" with the newer Mocha...

@apellerano-pw the specific issue is https://github.com/emberjs/ember-mocha/blob/master/vendor/ember-mocha/ember-mocha-adapter.js, which allows the "implicit async helper chaining tests" where you use `andThen()` instead of calling `done()` at the end or returning a `Promise`. that...

I'm having a hard time reproducing the issue from the information above. If this issue is still relevant, could someone create a reproduction repository on GitHub? otherwise this seems hard...

FWIW the main advantage of a template-only component might be that it puts less memory pressure on the garbage collector because the backing class is shared between all of those...