Async specs shortcomings about opal-rspec

[adambeynon]

@meh is this still relevant?

[wied03]

@meh - another thing i've noticed is that the reporter summary totals don't include failed async tests and the exit status of the text formatter/rake task doesn't include a failure if these fail. Maybe we could refactor these to use a Jasmine like approach, which uses a done object passed to the async block and the runner can asynchronously wait (check in periodically for the done call)? On a related note, the AsyncRunner class doesn't seem to be fully used to actually run the specs either. I removed it from the code and the specs all passed (just the summary broke).

[wied03]

Actually, re: the last sentence on my last comment, the only reason the summary broke was because when I yanked out the AsyncRunner, I took this block with it:

run_async_examples do
   self.finish
end

It appears the AsyncRunner was not doing anything.

[wied03]

See #17

[wied03]

@adambeynon @meh - I think this can also be closed since master has refactored this.