Keep in mind my comment has little context into whats going on in the greater picture but I wanted to comment on something that Ben said.

"f I am reading this correctly, this test case depends on the previous test case running before this one."

I think its best practice in all cases to ensure one test does not depend on the success of any other. Setup/teardown steps are designed to handle this case and mocha makes it really easy to extract common logic out into functions that can be re-used by tests. That aside mocha and test-agent don't make any attempts at cleaning up state at any point during the tests automatically... If a test depends on another its very likely it will break other things in unpredictable ways inside your apps tests.

I would highly recommend fixing any test files with that behavior and file bugs where this behavior is seen (in any of the app's test files).

Please reach out to me if there is something I am missing here or a need in the test frameworks that we have that cannot address some specific need/concern.