Updating some tests now, but they seem to be related to infra changes, not to this PR

It looks like test-runtime.js has some tests for this. E.g. see "should stop broadcasting after force-close". Possibly would be good to add this there.

/to @dvoytenko I'm not sure what you mean wrt that test in your previous comment. What should I do with it?

/to @rsimha I modified _init_tests.js to allow duplicate error messages in expectAsyncConsoleError, since some of these tests throw the same error message twice. Is there a reason why you didn't allow duplicate error messages in the first place? I was also thinking that this API should accept RegExp, not just complete strings, and that we can have a 2nd optional parameter to mark that an error should be expected n times (instead of calling this method twice with the same params). wdyt?

I think @alanorozco has already made it so you can pass in a regex. And yeah, optionally passing in a count sgtm.

Yup, it now accepts regex!

@danielrozenberg here's an idea of the test, similar to the "should stop broadcasting after force-close". Stub document.contains to always return false and try to purge the doc. It should stay b/c now it will always return true by isConnected.

@dvoytenko PTAL