Andrew Pellerano

I think v1.0 should drop support for the two older styles of test helpers (`describeComponent`, `setupComponentTest`, etc) now that Ember has unified testing. That will make this project a lot...

I want to update the yarn.lock (even though the README says to use npm) but I keep getting this error. Anyone know how to get around this? I don't use...

Ahh, I see. I know it says not to at the top... but I edited yarn.lock to replace the yahoo registry entry with the one you get doing `yarn add...

No, I'll start testing this with other projects using ember-mocha and report back. It's gonna take me some time to get to as my upcoming weekend is already full

Tested this on Ghost-Admin, it seems to break in tests with `done` hooks. Needs further investigation

I think my approach to squelching the overspecification error is wrong. It might have to go in the other direction and modify the wrapper function in the adapter to always...

@Turbo87 I've been messing around with mocha@3 in this project. I'm still a little confused as to exactly what is holding back the upgrade, likely because I'm new to this...

I have it working and tested with the new `.only` behavior. For the overspecification issue, I made every `it` use the `invoke` wrapper (previously fns with arity=1 were passed straight...

@jasonworden I think this repo has updated a bunch since I was last looking into this issue. My old PR is still viewable here: https://github.com/emberjs/ember-mocha/pull/216 There was a ` vendor/ember-mocha/ember-mocha-adapter.js`...

Thanks for the report. I don't use twitter at all so they probably changed their layout since I last updated the rules