tobi hangs about tobi

[tj]

do you app.close() at some point?

[sebs]

No, I dont. ;) Should I do that in the tests? ;)
(Captain Obvious again kicked me in the butt)

[tj]

:) unlike assert.response() no effort is made to auto-close the server since it is not uncommon to nest requests

[kvz]

I'm running tobi against a remote website, so without app.
All tests pass but the process remains open for me as well. How should I close it in my case?

[tj]

you can access the http client via browser.client so you can call close() etc when you are done

[kvz]

Thanks : )
I found that for servers that set the Transfer-Encoding: chunked header, a

browser.client.end()

will not do anything. On other servers it works as expected.
For now I think I can just

process.exit(0)

but It'd be cool if there was a nicer way to achieve this.

[timoxley]

+1 for "nicer way to achieve this"

also browser.client no longer exists, is there perhaps something else I can try? Mainly cause I can't use process.exit() from within a nodeunit test without it complaining.

[tj]

I cant think of a nicer way to deal with this sort of thing. If you're not nesting requests it's possible to just use a number to count the pending requests and auto-close the server, which is what I do with assert.response(), however Tobi stuff is almost always nested so that does not work. I'm making sure that with my Expresso successor that the test framework explicitly exit()s to prevent this sort of headache

[timoxley]

I'm interested as to what is actually preventing the process from quitting?

[tj]

the server is still listening for connections