feat(testing): add Done provider for tests that need more async control - #8159

cc @wardbell @jeffbcross

LGTM!

2 Travis jobs are failing on:

../../../../../tmp/test.typings/1461183968319/testing/ts/testing.ts(95,58): error TS7006: Parameter 'service' implicitly has an 'any'

And another job looks like a pub flake.

@juliemr can you shed some light on this? When exactly is this needed? I thought the new async() function takes care of this?

@PascalPrecht This is for rare situations where you can't use async. Most users should never need it.

An example would be if you have a setTimeout and you really want to test something that happens on the third iteration.

Travis is happy now - adding to merge queue.

Putting this on hold while @vikerman investigates a different method.

FYI - the method we're investigating would look something like:

it('does foo', (done) => {
  inject([Service}, (service) => {
    doStuff();
    // sometime later asynchronously
    done();
  });
});

Will instead allow use of done and inject with #8257

See particularly example like #8257 (comment)

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}