Timeout triggers new test and blows away client-side debugger state. #17

mojit0 opened this Issue Sep 28, 2012 · 1 comment


None yet
2 participants

mojit0 commented Sep 28, 2012

If you have a debugger statement in a client-side test the next test will start and cause your debugger to reset. There's no way to tell arrow not to time out.

proverma pushed a commit that referenced this issue Mar 14, 2013

I think its related to #16 , and should not be an issue any more, as its all part of same process. please reopen if thats not the case.

@proverma proverma closed this Apr 25, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment