Should we also restore the original timeout? (Since this unit test actually runs in Brackets, and the node server is a singleton, the timeout actually affects everyone.)

Hmmm. I had forgotten that these unit tests actually were running from Brackets, as opposed to just on the node code directly. That makes things like setting the timeout temporarily a little dicey, especially since it happens asynchronously. I wonder if we should have a general way of loading a "test" version of a node domain so that we can be sure not to accidentally mess up the real version of that domain.

(That might be a reason not to set the timeout too short...)