[andrewdavey]

Reducing tight coupling is definitely a concern I'm looking into. I can't see there being any silver bullets, but a good framework should certainly encourage a sustainable way of working.

I've developed a rather nice asynchronous, sequential, execution model for test code. So they avoid the callback-hell you'd see with multi-step async tests. The spin assert idea mentioned in the article is very useful, and I'll be borrowing it for sure! :)

I'm wary of running tests in parallel, due to concurrency issues. However, I guess spinning up multiple web servers and in-memory databases would work fine.