quick hack to prevent Chrome debugger from locking up due to recursive nature of test runs in 2.0: this is akin to a stack overflow attack as 3every single test adds another series of stack frames as each test is always treated as 'asynchronous' without separating them via a timer or similar stack-killing devices.