I don’t think it would make sense to have a default test timeout (because it would have to be insanely long, like minutes or so; tests are very different), and the SingleExpectDefaultTimeout was chosen as a reasonable “we expect a response right now” thing which survives mild machine troubles (but as we know fails sometimes). Making it much larger does not gain much.

Also: how exactly did you envision your “implicit within” to work? Write our own test framework? (this is not meant inflammatory, you know)

Anyway, we don’t have time to rework our test suite right now, so let’s add a `within` here and be done with it. We can revisit this when 2.2 is out.