WIP: expectAssertion updates for RFC 232 compat

[alexdiliberto]

No description provided.

[cibernox]

I entered the repo looking for this. What is missing on this? May I help?

[rwjblue]

@cibernox - Likely needs some "dusting off" and bug fixing (since CI is failing). I think the main changes to the expectAssertion functions are based on my wip here: master...async-wip. We'd love someone to tackle this and push it over the hump...

[alexdiliberto]

@cibernox Hit a bit of a roadblock described here #18 (comment) and haven't had a chance to look at it again. Please work on it if you have some spare time, would love the help!

[cibernox]

@alexdiliberto @rwjblue I've started by an update-only PR (#23) to separate the wheat from the chaff.

[shokmaster]

Hi guys! Any news about this issue? We're having problems with the function expectAssertion in our project. We're patching a setupExpectAssertion() based on #18 (comment) but it's a bit unestable in some scenarios.

Perhaps it would be convenient to update the async-wip branch with the @cibernox PR (#23) and separate the framework/CLI update from the adaptation to the RFC.

Let me know if I can help in any way. Thanks in advance!

[stefanpenner]

I am upstreaming these assertions into ember-qunit

I will review this PR, and try and incorporate appropriate changes upstream.

When all this lands, my plan is to deprecate this library entirely in-favor of it's assertions simply being officially supported: #29