teardown

[cloudhead]

We need a teardown stage.

[qrush]

(+1) Just sticking it into topic now, feels ugly.

[cloudhead]

I just pushed a new version (0.5.1) with basic teardown support. It's really simple, so it might still need some revisions, but it would be nice to get some feedback on it.

Usage is simple:

teardown: function (topic) { ... }

The teardown will be run after the assertion functions in its context, independently of where it's placed.

[luebken]

Works great for me. A documentation update would help.

[koudelka]

It looks like the teardown function doesn't wait until sub-contexts have completed their tests. Is that intentional?

[cloudhead]

@koudelka, that's the expected behavior, yes. Having it happen after sub-contexts would be useful, and what I wanted initially, but it's much more complex, so it'll have to wait.

[leei]

+1 for the 'after subcontexts' teardown. The teardown is pretty useless if there are such subcontexts, since they almost certainly depend on the state established by the enclosing topic (e.g. setting up a redis connection).

[paulbjensen]

+1 for doc update. Needed this feature real badly, glad to see it's there.

[alexgorbatchev]

we also need a teardown/startup for the bundle (ie spin up an http server and shut it down at the end)

[seebees]

@cloudhead, this looks like it's done. sub-contexts and all. I don't see the documentation in the project but I think all that this issue can be closed? And the documentation be updated? Not sure how to help with that...

[afeld]

+1 on documentation needed

[dervalp]

+1 for documentation :)

[indexzero]

Going to leave this open as a documentation bug.

[indexzero]

Actually going to close this as a duplicate of #214